Because GPL. Either kernel is GPL or not. If it is (and as you say it is) then same rules apply to all programs distributed under conditions of GPL.
One is always free to add special execptions, in the case of Linux, that is exactly the case. And if kernel and glibc interact certain wai that allows kernel to be GPL and glibc LGPL then there are certain conditions that allows it. glibc and Linux are not linked together. Could you please be clear about what kernel you are speaking of? There are many kernels, and Linux is not the only one that works with the GNU system. I will assume you are talking about Linux here. Weird: Note that according http://www.linuxrising.org/files/licensingfaq.html you cant hide closed soft under layer of GPL->LGPL->closed source, however there is case kernel->glibc->adobre reader. But Linux is notw being linked to glibc, nor is glibc being linked to Linux. So the tree you show is not correct. glibc talks to Linux, yes, it does not link to it. You talk to bash, you do not link to it. What of this is hard to understand? You talk to a telnetd, you do not link to it. This is the exact same situation with Linux and glibc. There is a protocol which Linux supplies, which glibc uses. Again, glibc _does_not_link_ to Linux. Cheers. _______________________________________________ gnu-misc-discuss mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-misc-discuss
