linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <or4pl8yky7.fsf@oliva.athome.lsd.ic.unicamp.br>
Date:	Fri, 15 Jun 2007 18:19:44 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
Cc:	Ingo Molnar <mingo@...e.hu>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Daniel Hazelton <dhazelton@...er.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, david@...g.hm,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Jun 15, 2007, lsorense@...lub.uwaterloo.ca (Lennart Sorensen) wrote:

> On Thu, Jun 14, 2007 at 11:21:59PM -0300, Alexandre Oliva wrote:
>> Consider egg yolk and egg shells.
>> 
>> I produce egg yolk.  I give it to you under terms that say "if you
>> pass this on, you must do so in such a way that doesn't stop anyone
>> from eating it"
>> 
>> 
>> You produce egg shells.  You carefully construct your shell around the
>> egg yolk and some white you got from a liberal third party.
>> 
>> 
>> Then you sell the egg shells, with white and yolk inside, under
>> contracts that specify "the shell must be kept intact, it can't be
>> broken or otherwise perforated".

> It would be more like not telling you how to change the egg yolk while
> still having a working egg.

This might be more like GPLv3, or it might not.  But it still misses
the point.

The point is to show that the egg yolk license still is about the egg
yolk license, even though its effects do limit what the egg shell
manufacturer can do with that particular egg yolk.

I.e., the GPL is still about the software, and the hardware
manufacturer can't claim "but this is the hardware!" to escape
obligations determined by its choice of the GPL software.

>> Are you or are you not disrespecting the terms that apply to the yolk?

> Very bad comparison.  

Very bad understanding of the intent of the argument, and failing to
answer the relevant question ;-)

> What if I want to run a program that takes 512MB ram and the hardware
> guys put in 128MB.  Now they are impeding me doing the change I wanted
> to do to the software.

*Why* did they make this decision?

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@...d.ic.unicamp.br, gnu.org}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/