3 ms·
Imagine Linux relicensing under the AGPL. I don't think that's the setup Linus wants.
by tyingq 6y ago
Imagine Linux relicensing under the AGPL. I don't think that's the setup Linus wants.
- remram 6y agoWhat would it imply? Programs running on Linux are already considered not "linked" to Linux, which means they can stay closed source without breaking the terms of the kernel's GPL license. That likely wouldn't change if the kernel was AGPL: programs running on it wouldn't need to be AGPL. So the difference would be that for direct interaction with a Linux system, the source code of the kernel would need to be released (the kernel itself, not programs)? That doesn't sound too hard at all.
- tyingq 6y agoThe article says linking OR use over a network...
- remram 6y agoThe Linux project has made it clear that apps running over it are not linking with it and therefore not derivatives for GPL (and AGPL) purposes. Releasing the source of your kernel is no problem at all.
- deleted 6y ago[deleted]
- mr_toad 6y agoAWS and other cloud vendors would have to distribute any changes they made to kernels they run in the cloud (e.g. Amazon Linux). Why would that be a problem?
- mort96 6y agoYea, the big issue with licensing Linux as AGPL would probably be that Linus explicitly doesn't like GPL3's ant-Tivoization stuff. Requiring SaaS providers to distribute their kernel patches is, I believe, completely in line with the goals of Linus's choice of license.