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: <alpine.LFD.0.98.0706141100390.14121@woody.linux-foundation.org>
Date:	Thu, 14 Jun 2007 11:06:32 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Alexandre Oliva <aoliva@...hat.com>
cc:	Adrian Bunk <bunk@...sta.de>, Valdis.Kletnieks@...edu,
	Daniel Hazelton <dhazelton@...er.net>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, 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>, mingo@...e.hu
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Thu, 14 Jun 2007, Alexandre Oliva wrote:
> 
> Let me see if I got your position right: when TiVO imposes
> restrictions, that's ok

Sure. I think it's ok that Microsoft imposes restrictions too on the 
software they create. It's *their* choice.

And I think it's ok for you to impose any restrictions (including the ones 
in GPLv3) on the software *you* produce. It's your choice.

> but when others want to find ways to stop it, then it's not.  *Now* I'm 
> confused ;-)

You are indeed totally confused.

It's *ok* to impose restrictions on the stuff you create. Everybody has a 
different world-view, and for some it's about making money, for some it's 
about something else, and some don't want any restrictions at all.

For me, the GPLv2 was the license I liked. I didn't like the BSD license, 
so I didn't choose it. I don't like a license that restricts hardware, so 
I didn't choose that.

And I *still* don't choose that.

See? I think the GPLv3 is a *much* inferior license to the GPLv2. It's 
better than its drafts were, but it's still doing things I disagree with. 

So tell me, why do you think I'm confused about the GPLv3? Why do you 
think I should have said "GPLv2 or anything else the FSF comes up with"? 

So the only thing I want you to say is:

 (a) Linus knows what he is doing, and isn't actually confused.

and

 (b) It was my right to use the license of my choice for a project that I 
     started.

and

 (c) I have the right to see the difference between the GPLv2 and v3, and 
     think that the GPLv3 is the inferior license.

Comprende? MY CHOICE. Not the FSF's. Not yours. Not anybody elses.

		Linus
-
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/