Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

From: Tarkan Erimer
Date: Sun Jun 10 2007 - 04:37:59 EST

Hi David,

David Schwartz wrote:
But; if the Linux kernel should Dual-Licensed (GPL V2 and GPL V3), it
will allow us the both worlds' fruits like code exchanging from other
Open Source Projects (OpenSolaris etc.) that is compatible with GPL V3
and not with GPL V2 and of course the opposite is applicable,too.

That is a misleading claim. While being dual-licensed would make it either
for other projects to adopt Linux code, it would have three downsides:

1) If Linux code were adopted into other projects that were not
dual-licensed, changes could not be imported back into Linux unless the
changes were dual-licensed which is not likely when the contributions are
made to a project that's not dual-licensed.

2) Linux could no longer take code from other projects that are GPL v2
licensed unless it could obtain them under a dual license.

And, last and probably most serious:

3) Linux derivatives could be available with just a GPL v3 license and no
GPL v2. license if the derivers wanted things that way.

Thanks for the corrections ;-) The whole picture is more clear now for me :-)
BTW,I found a really interesting blog entry about which code in Linux Kernel is using which version of GPL :

The work done on a Linux 2.6.20. The result is quite interesting. Because almost half (Around %60 of the code licensed under "GPLv2 Only" and the rest is "GPLv2 or above","GPL-Version not specified,others that have not stated which and what version of License has been used) of the code is "GPLv2 or above" licensed. And also stated in the article that some of the codes should be "Dual Licensed" not the whole Linux kernel needed to be "Dual Licensed". So,if it is really like this, maybe we can make,for example: "File system related Codes", "Dual Licensed" and it will allow us to port ZFS from OpenSolaris requested by a lot of people or other things maybe ?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at