lkml.org 
[lkml]   [2007]   [Jun]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
On 10/06/07 09:37, Tarkan Erimer wrote:
> BTW,I found a really interesting blog entry about which code in Linux
> Kernel is using which version of GPL :
>
> http://6thsenseless.blogspot.com/2007/02/how-much-linux-kernel-code-is-gpl-2.html
>
>
> 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 ?

Once code obtained under the GPLv2 only licence that the kernel is released
under is modified and submitted back to Linus for inclusion, that code
would become GPLv2 only - only the original would be BSD/LGPL/GPLv2+ and
only separate changes to the original could continue to be available under
dual licence. Since most files will have been modified at various stages
in Linux's development when major internal changes occur, surely practically
everything is now GPLv2 only?


> So, does it mean we can change the license of the dead people's code ?

If you can contact whoever currently owns the copyright, they can release
it under another licence... however this is no good because the derivative
work would be GPLv2 only. Perhaps if you got *everyone* at all stages of
development (including code that has been removed if existing code is a
derivative work of it) to agree - then it could work.

It only takes one person's code, uncooperative or not contactable, to
prevent a change to the licence, so there's not much point in trying
unless you intend to start replacing such code.


On 10/06/07 10:03, Jan Engelhardt wrote:
> You've got to take MODULE_LICENSE() into account. There is
>
> MODULE_LICENSE("GPL");
> MODULE_LICENSE("GPL v2");
> MODULE_LICENSE("GPL and additional rights");
> MODULE_LICENSE("Dual BSD/GPL");
> MODULE_LICENSE("Dual MIT/GPL");
> MODULE_LICENSE("Dual MPL/GPL");

Surely that doesn't work since the entire Linux kernel is (and can only be)
released as GPLv2? Wouldn't anyone making changes to those files need to
obtain a copy under the other licence and explicitly release it under both
licenses in order to maintain that?

--
Simon Arlott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-06-10 11:19    [W:1.229 / U:11.952 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site