On Wed, Sep 26, 2001 at 12:17:37PM -0700, Crispin Cowan wrote: > Greg KH wrote: > > >If you were to include a GPL licensed user space header file in a closed > >source program, of course you would be violating that license. > > > That is not clear to me. I have been unable to find a definitive > reference that states that is the case. If so, it is problematic, > because then every user-land program that ever #include'd errno.h from > glibc is GPL'd, because glibc #include's errno.h, among other GPL'd > kernel header files. Are you sure you want to declare nearly all > proprietary Linux applications to be in violation of the GPL? That is an issue to take up with the glibc authors, not me. If something like this bothers you, then use a libc that does not include kernel header files (which has been pointed out by the kernel authors that they should not be doing.) dietLibc [1] works for me quite well and does not contain any kernel header files. > If you (Greg, Alan) are confident that your interpretation of the GPL is > correct, then just marking the files as GPL should be sufficient. What > purpose is served by saying anything else? As Alan stated, to reduce confusion as to the wishes of the copyright holders of the file. 3 out of the 4 current holders agree to this wording, and as the dissenting party, you are free to disagree and keep that wording from the file (however a small note in it detailing this disagreement might be a nice thing to do.) thanks, greg k-h [1] http://www.fefe.de/dietlibc/ _______________________________________________ linux-security-module mailing list linux-security-moduleat_private http://mail.wirex.com/mailman/listinfo/linux-security-module
This archive was generated by hypermail 2b30 : Wed Sep 26 2001 - 13:07:47 PDT