Re: Binary only module overview

offerat_private

* frm gregat_private "09/26/01 10:05:19 -0700" | sed '1,$s/^/* /'
*
* On Wed, Sep 26, 2001 at 05:17:51AM +0000, David Wagner wrote:
*> 
*> <TANGENT>
*> (By the way, there is a difference between the word "include" and the
*> cpp syntax "#include".  They have seven letters in common, but it's not
*> clear that the two notions are necessarily equivalent when it comes to
*> licenses like the GPL.  To take this to an absurd extreme, one might
*> argue that any non-GPL user-level application running on Linux dare not
*> # include anything in /usr/include/linux/, but it is pretty hard for me
*> to see how such a position could be plausible.)
*> </TANGENT>
* 
* User programs should not be including anything from /usr/include/linux.
* It is glibc's problem if it does that (I think it has been fixed in the
* latest few releases.)  Other system libraries do not include anything
* from that directory (dietLibc, uClibc, etc.)
* 
* So yes, that argument is valid :)

It that case it's not possible to have anything that uses libc (LGPL) be
anything that isn't GPL compatable. That could well hamper Linux acceptace
in some markets.

errno.h -> bits/errno.h -> linux/errno.h

However since linux/errno.h does not have a GPL copyright on it (neither do
most of the header files in linux/*) it could be argued that they are in
fact freely redistributable since they are there purely to document a
functional interface (the term "functional" is important as that conveys no
artisitic content and therefore copyright applies differently).

* 
* greg k-h
* 

richard.

-----------------------------------------------------------------------
Richard Offer                     Technical Lead, Trust Technology, SGI
"Specialization is for insects"
_______________________________________________________________________

_______________________________________________
linux-security-module mailing list
linux-security-moduleat_private
http://mail.wirex.com/mailman/listinfo/linux-security-module