2 ms·
I wish people would stop trying to work around the GPL. It causes immense heartache and someday, the kernel developers will revolt and destroy any avenue that y
by Conan_Kudo 6y ago
I wish people would stop trying to work around the GPL. It causes immense heartache and someday, the kernel developers will revolt and destroy any avenue that you try to use. After all, that's what just happened with the NVIDIA GPU drivers with Linux 5.9.
Also, you're still pulling in parts of Linux into your code, so GPLv2 still applies.
- tyingq 6y agoI don't see how that would apply to an application using io_uring through syscalls. It's not linking to any GPLv2 code, and the header file (io_uring.h) is dual licensed as GPLv2 and MIT. Similarly, if you choose to use the higher level liburing, it's dual LGPL and MIT licensed. It's all very deliberately not viral for user-space applications.
- Conan_Kudo 6y agoThat is not true for eBPF, though. That stuff pretty works exclusively out of instrumenting and manipulating Linux itself. That said, libbpf is LGPLv2+, even though a lot of the stuff you'd pull in to use eBPF at the kernel level forces it to be GPLv2.
- MaxBarraclough 6y agoThe 'workaround' will be for companies to use it for internal projects, and to decline to publish their work. The kernel is licensed under GPLv2 after all, not the AGPL.