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:	Thu, 14 Jun 2007 23:56:19 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Daniel Hazelton <dhazelton@...er.net>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Alexandre Oliva <aoliva@...hat.com>, Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>,
	"david@...g.hm" <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

> A hundred or so messages back someone stated that the parport driver in Linux 
> is GPLv1.1 - however, on checking on this statement for myself I've found 
> that there is no statement about it being v1.1 and, in fact, given that Linux 
> itself is GPLv2 there is no possible way any code covered by GPLv1.1 can 
> exist.

Wrong again.

If a piece of code was merged into the kernel with a GPL v1 "or later"
license then it still has a GPL v1 "or later" license.  The "or later"
makes it compatible with the v2 code but does not change the fundamental
copyright on the original work that was combined. Thus if you could
identify specifically a GPL v1 work within the kernel you could use that
GPL v1 work as per GPL v1 providing you didn't mix it with v2 code.

If I take a public domain book and create a derivative work from it the
original work does not magically become restricted.

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