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]

Date:	Fri, 15 Jun 2007 15:29:05 +0100
From:	Paulo Marques <pmarques@...popie.com>
To:	Bernd Paysan <bernd.paysan@....de>
CC:	Al Viro <viro@....linux.org.uk>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Krzysztof Halasa <khc@...waw.pl>, linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

Bernd Paysan wrote:
> On Friday 15 June 2007 13:49, Paulo Marques wrote:
>> I've contributed some code for the kernel (unlike yourself, AFAICT), and
>> believe me, I did so under GPL v2. The COPYING file is pretty much self
>> explanatory, so I didn't need to add any explicit license statement to
>> my code.
> 
> It's not, it's a personal comment from a misunderstanding of the GPL text. 
> It's as valid as the "closed source kernel modules are legal" comment that 
> was there some years ago.

These are not changes to the license text. These are just clarifications 
to help people understand the license. They don't change what the 
license already said.

>> People seem to forget that the kernel license in COPYING *never had* the
>> "v2 or later" clause. Never. Period.
> 
> It's there in section 9.

The section 9 is meant to explain how you select one version of the 
license in a program without having to copy the entire license text to 
it, i.e., in simple programs you can just put the small text, suggested 
by FSF at the bottom of the gpl, and have the version number there, and 
that should be enough to reference the entire text.

But COPYING *is* the entire text and starts with: "
		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991"

so there is no confusion about the version.

>>[...]
>> And people who write kernel code are perfectly aware that the kernel
>> license is GPL v2 only, and always has been (except for the initial
>> linus license).
> 
> Wrong.

Why do you say "Wrong"? Have you contributed some code to the kernel 
thinking that the kernel was "v2 or later", only to find out later that 
it wasn't?

In case you haven't followed previous discussions, here's a pointer:

http://lkml.org/lkml/2006/9/22/176

The major kernel developers (and probably most of the total number of 
developers) are perfectly aware of the kernel license and chose GPL v2.

I'm getting pretty tired of listening to people that just _know_ what I 
should do with _my_ code. And people who treat kernel developers as 
morons who can't read a license.

We definitely need more Al Viro style comments on this thread ;)

-- 
Paulo Marques - www.grupopie.com

"The Mexicans have the Chupacabra. We have Al Viro. If you hear him 
roar, just _pray_ he's about to dissect somebody elses code than yours.. 
There is no point in running."

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