From: Arjan van de Ven <arjanv@redhat.com>
To: Crispin Cowan <crispin@wirex.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Christoph Hellwig <hch@infradead.org>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
Linux Security Module <linux-security-module@wirex.com>
Subject: Re: [PATCH] make LSM register functions GPLonly exports
Date: 17 Oct 2002 20:03:55 +0200 [thread overview]
Message-ID: <1034877846.3006.2.camel@localhost.localdomain> (raw)
In-Reply-To: <3DAEF703.20009@wirex.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Thu, 2002-10-17 at 19:44, Crispin Cowan wrote:
> Note that if we decide that #include of a kernel header file means that
> a work is derived, then we cause another problem: most Linux
> applications come under the GPL. glibc #includes some kernel header
> files, and most Linux applications #include glibc headers, so most
> applications are #including kernel header files. If #include is the
> basis for declaring a module to be a derived work of the kernel, then
> there is some bad news coming for people who like to use Oracle and DB2
> on Linux ...
>
difference is that glibc only uses the glibc-kernheaders; which on
several distros at least are just the data structures and not the
inlines. (and the inlines are in #ifdef KERNEL anyway and removed by the
preprocessor for userspace)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-17 17:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 14:35 [PATCH] make LSM register functions GPLonly exports Christoph Hellwig
2002-10-17 15:07 ` Greg KH
2002-10-17 15:13 ` Christoph Hellwig
2002-10-17 16:21 ` Jeff Garzik
2002-10-17 16:51 ` Crispin Cowan
2002-10-17 16:54 ` Christoph Hellwig
2002-10-17 17:08 ` Linus Torvalds
2002-10-17 17:20 ` Greg KH
2002-10-17 17:25 ` Linus Torvalds
2002-10-17 20:39 ` Ingo Molnar
2002-10-17 17:44 ` Crispin Cowan
2002-10-17 18:03 ` Arjan van de Ven [this message]
2002-10-17 17:20 ` Richard B. Johnson
2002-10-17 17:26 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1034877846.3006.2.camel@localhost.localdomain \
--to=arjanv@redhat.com \
--cc=crispin@wirex.com \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox