To view parent comment, click here.
To read all comments associated with this story, please click here.
Actually, he may be right about that... HOWEVER, if that is to happen, it will be done with a GPLv3 with added permissions to make it functionally equivalent to the LGPL. I believe there were musings about constructing a sort of "new LGPL" that way.
I fairly often see people who appear to underestimate the FSF a bit. The FSF may have strong principles and ideology, but that doesn't mean they're stupid. They compromise, they are realistic, and often practical about what they do.
They're quite aware that making the GNU stack incompatible with the Linux kernel (either legally or technically) is probably on the list of the "10 most stupid things the FSF could do". Likewise is putting glibc under a pure GPLv3 licence (thus forcing all code compiled using glibc to become GPLv3. Cool in theory, but a really stupid move in practice).
"""
unless the software is using glibc which is under LGPL. but that may change, so future glibc will be under GPLv3. and any software using glibc cannot run under linux kernel.
"""
No. "system software", software which may generally be expected to exist on a particular platform, is exempted. Otherwise, you wouldn't be able to run GPL software on Windows, etc.
I think that the Linux kernel and glibc both qualify as "system software" on most Linux systems. :-)
Edited 2007-06-13 18:19





Member since:
2006-01-03
unless the software is using glibc which is under LGPL. but that may change, so future glibc will be under GPLv3. and any software using glibc cannot run under linux kernel.