A discussion on combining CDDL and GPL code
A discussion on combining CDDL and GPL code
Posted May 27, 2016 17:25 UTC (Fri) by asaz989 (guest, #67798)In reply to: A discussion on combining CDDL and GPL code by pboddie
Parent article: A discussion on combining CDDL and GPL code
That is exactly what the derived-works discussion is all about. It is widely assumed that any kernel module is a derivative work of the kernel (and hence the GPL applies), and Canonical is acting like that just ain't so. There is some arguing in the alternative going on with the "spirit of the GPL" defense, but the core issue comes down to "what is a derived work of the kernel and what is not".
Posted May 27, 2016 21:19 UTC (Fri)
by pboddie (guest, #50784)
[Link]
This has previously been discussed in the context of the Nvidia drivers which supposedly use the same code as the ones used on Windows, and so people like to claim that the Nvidia drivers could never be derived works of Linux. But the derived works discussion is not about those drivers in their "inert" state.
When considering the GPL, I like to consider the "view source" scenario: you're running Linux combined with the ZFS implementation delivered by Canonical; Linux is GPL-licensed and thus imposes certain conditions about it being combined with other things and the source code for the result being available (for further distribution under the GPL's terms); therefore, the complete source code for that running system must be available to the end-user. Can this really be satisfied if the source of the ZFS implementation cannot actually be obtained and redistributed under the GPL?
Naturally, people may argue (just as they do with the Nvidia drivers) that it's the user who combines the works and that no-one is actually distributing the combination. Others may argue that the different parts of the running system do not comprise a derived work of one of those parts. Such matters I will happily leave to the lawyers to argue about.
A discussion on combining CDDL and GPL code