Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761582AbXF1RlL (ORCPT ); Thu, 28 Jun 2007 13:41:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753786AbXF1Rk5 (ORCPT ); Thu, 28 Jun 2007 13:40:57 -0400 Received: from lsd-gw.ic.unicamp.br ([143.106.7.165]:54102 "EHLO boneca.lsd.ic.unicamp.br" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753249AbXF1Rk5 (ORCPT ); Thu, 28 Jun 2007 13:40:57 -0400 To: davids@webmaster.com Cc: Subject: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3? References: From: Alexandre Oliva Date: Thu, 28 Jun 2007 14:40:39 -0300 In-Reply-To: (David Schwartz's message of "Wed\, 27 Jun 2007 23\:15\:29 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2176 Lines: 48 On Jun 28, 2007, "David Schwartz" wrote: >> Let's hope courts see it this way. >> 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? > You can use the hardware to stop someone from copying or modifying some > particular copy of the source code, so long as there is some copy of the > source code they can copy and modify. You are equivocating between a > particular copy and any copy at all. How do you reach this conclusion as to this kind of distinction? > I agree. You have the legal GPL right to modify any copy of a GPL'd work, > provided no technical or authorization obstacles stand in your way. Hey, why stop at these excuses to stop someone from modifying copies of the GPL? Why not list legal obstacles as well? > If the source code is on CDROM, you cannot modify that particular > copy even though you have the legal right to modify "the source > code". Yup. > The GPL does sometimes use the word "may" where it's not clear whether it > means you have permission or you must be able to. The general rule of > construction is that "may" means permission, unless there's some clear > indication to the contrary. The "may"s in sections one and two are > permisssion against a claim of copyright enfrocement. The "further > restriction" clause is, at it states, only on the exercise of *rights* > (which I think means those rights licensed to you under copyright law, > namely the right of distribution and copying). ... and modification and, depending on the jurisdiction, execution. -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ FSF Latin America Board Member http://www.fsfla.org/ Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org} Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org} - 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/