And your point? My point is - we have GPL kernel -> we use it as a library, yet we can use some other license for program. We cant do it with standard GPL library.
glibc and Linux do not share any code in linking. Linux doesn't do a dlopen(), nor does glibc do a dlopen() against Linux. The license of glibc has nothing to do with the license of Linux, but the fact that all user space would have to be GPLed if glibc was under the GPL. > You are spreading misinformation. Possible as side effect. My goal is to understand, why programs using kernel can be not-GPL, while programs using GPL library has to be GPL. Because Linux has a special execption that allows for this. Most GPL libraries do not. About using GPL library means GPL program or kernel. The only difference I see is that calling kernel requires filling certain registers and calling int 0x80 (on i386), while calling function require pushing arguments on stack and jump to certain adress. In both cases it will end up on some address in memory, where computer will do some thing and returns back. Code is actually shared when you link something to glibc, it is not shared between glibc and Linux. int 0x80 (on x86) is more like fork/exec. _______________________________________________ gnu-misc-discuss mailing list gnu-misc-discuss@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-misc-discuss
