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: <d120d5000706150541g31dfd0c5ue86e99ede146a387@mail.gmail.com>
Date:	Fri, 15 Jun 2007 08:41:45 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Bernd Paysan" <bernd.paysan@....de>
Cc:	"Paulo Marques" <pmarques@...popie.com>,
	"Al Viro" <viro@....linux.org.uk>,
	"Krzysztof Halasa" <khc@...waw.pl>, linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On 6/15/07, Bernd Paysan <bernd.paysan@....de> wrote:
> On Thursday 14 June 2007 19:20, Paulo Marques wrote:
> > Watching the output of the first grep without "wc -l" shows that,
> > although it is not 100% accurate, it is still ok just to get a rough
> > estimate.
> >
> > So yes, ~6300 files are definitely more than a couple ;)
>
> Most of them don't say anything, so they are "any GPL" by the author.

Woah! Stop right there. Since when a work without a license spelled
out becomes "any GPL"?

> When
> do you people accept that Linus can't change the GPL, he can only add
> comments of what he thinks is the case! His interpretation of the GPLv2
> might be that not saying anything about the version means "v2 only", but if
> he does so, he's simply wrong. He was wrong in the module case, as well,
> and dropped this comment a while ago. He might drop this comment in future,
> as well. In fact, anybody can drop this comment, as it's just a comment.
>
> The kernel *as a whole* is clearly under GPLv2 only from Linus' comment,
> which is in fact true, since the common subset of GPL versions from all
> authors is indeed GPLv2 (by virtue of some files from Al Viro, and maybe
> some other explicit GPL v2 files). The author must specify the version
> himself, there simply is no other way. If you don't specify any, it's "any
> version", because I can license all patches straight from the authors.

Yes, you can. In this case you get _different_ software, maybe even
under different license. I bet if you go straight to the authors you
can get XFS or JFS under a commercial license, not GPL at all.

>  The
> way the GPLv2 allows you to explicitely specify "any version" is by not
> saying anything about the version at all.

Let me quote GPLv2 for you:

"If the Program specifies a version number of this License which
applies to it and "any later version", you have the option of
following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation."

As you can see for "ant later version" to apply the program must
explicitely say "This program is distributed under GPLv2 and any later
version". Supplying text of GPL v2 with the program does not
automatically add that clause. IOW, if copying file would litrally
read "Distributed under GPL v2. For the text of GPL v2 go to
www.fsf.org" woudl you still argue that it is "GPLv2 and later"?

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