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:	Sun, 17 Jun 2007 22:28:17 +0200
From:	Bernd Petrovitsch <bernd@...mix.at>
To:	Alexandre Oliva <aoliva@...hat.com>
Cc:	Gabor Czigola <czigola@...il.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Sun, 2007-06-17 at 15:55 -0300, Alexandre Oliva wrote:
> On Jun 17, 2007, "Gabor Czigola" <czigola@...il.com> wrote:
> 
> > I wonder why the linux kernel development community couldn't propose
> > an own GPL draft (say v2.2) that is "as free as v2" and that includes
> > some ideas (from v3) that are considered as good (free, innovative, in
> > the spirit of whatever etc.) by the majority of the kernel developers.
> 
> For one, because the text of the GPL is copyrighted by the FSF, and
> licensed without permission for modification.  And that's as it should
> be, you don't want others to modify the terms of the license you chose
> for your code, do you?

That's probably precisely the reason for removing the "or later" so that
others (even if it's "only" the FSF) can't modify the terms of the
license chosen for the code.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services

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