3 ms·
The Linux kernel has explicit rules for the cases where it allows it: An explicit license exception for the syscall interface, stating that calling it from use
by detaro 8y ago
The Linux kernel has explicit rules for the cases where it allows it:
An explicit license exception for the syscall interface, stating that calling it from userspace is freely allowed: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/LICENSES/exceptions/Linux-syscall-note?h=v5.0-rc2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
And modules, e.g. drivers, have various statements from Linus on how they're not necessarily considered derived works of the kernel/linked to the kernel, e.g. http://linuxmafia.com/faq/Kernel/proprietary-kernel-modules.html http://linuxmafia.com/faq/Kernel/proprietary-kernel-modules.... or http://lkml.iu.edu/hypermail/linux/kernel/0312.0/0670.html http://lkml.iu.edu/hypermail/linux/kernel/0312.0/0670.html
- pedrocr 8y agoI know the situation of the Linux kernel. The discussion hinges on what is a "derived work". Kernel modules are very interlinked with the kernel, particularly since there are no stable APIs inside the kernel. It seems strange that just linking to a GPL library that defined an API makes you a derived work. But that is the FSF position: https://en.wikipedia.org/wiki/GNU_Readline#Choice_of_the_GPL_as_GNU_Readline's_license https://en.wikipedia.org/wiki/GNU_Readline#Choice_of_the_GPL... This is why I always do libs as LGPL but it seems strange to me that it's even needed. If I've defined a proper opaque API, to be consumed by external code I know nothing about, it's strange to then argue that library callers are derived works and LGPL is explicitly needed.