Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760140AbXF1ExU (ORCPT ); Thu, 28 Jun 2007 00:53:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752310AbXF1ExM (ORCPT ); Thu, 28 Jun 2007 00:53:12 -0400 Received: from keil-draco.com ([216.193.185.50]:50098 "EHLO mail.keil-draco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752413AbXF1ExL (ORCPT ); Thu, 28 Jun 2007 00:53:11 -0400 From: Daniel Hazelton To: Alexandre Oliva Subject: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3? Date: Thu, 28 Jun 2007 00:52:48 -0400 User-Agent: KMail/1.9.6 Cc: davids@webmaster.com, linux-kernel@vger.kernel.org References: <200706272251.48884.dhazelton@enter.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706280052.48543.dhazelton@enter.net> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1706 Lines: 40 On Thursday 28 June 2007 00:45:18 Alexandre Oliva wrote: > On Jun 27, 2007, Daniel Hazelton wrote: > > Section 3 doesn't apply to this situation. However, other sections > > do. They are distributing in line with the distribution requirement, > > but not the "modification and copying" requirements. These are > > granted early in the license and covered by the "no further > > restrictions" clause. > > > > You have to be able to copy and modify the source code for it to > > comply with the GPL. > > Let's hope courts see it this way. I'm sure they will. Section 0 of the GPLv2 states what the license covers. Copying & modification are two of those things. > But then, why is it that I can't use hardware to stop someone from > copying or modifying the source code, but I can use hardware to stop > someone from copying or modifying the binary? Or is that not so? As has been repeatedly stated, on a TiVO or similar device they can stop you from running a user-built binary. They cannot, and do not, stop you from accessing the copy on the disc. They don't even prevent modification of it. What they do is stop the hardware from running the modified form. > Remember, section 2 talks about modifying *your* *copies* of the > Program, without any reference whatsoever as to whether they're in > source or object form. I can't argue with this. DRH -- Dialup is like pissing through a pipette. Slow and excruciatingly painful. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/