From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bernd Eckenfels <ecki@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] DSFS Network Forensic File System for Linux Patches
Date: Sun, 04 Sep 2005 09:45:31 +0100 [thread overview]
Message-ID: <1125823531.23858.16.camel@localhost.localdomain> (raw)
In-Reply-To: <E1EBfWr-0004LP-00@calista.eckenfels.6bone.ka-ip.net>
On Sad, 2005-09-03 at 23:26 +0200, Bernd Eckenfels wrote:
> Loading a non-GPL (tagged) module leads in tainting the kernel (which basically
> is a flag for developers to be alerted while debugging), is that right?
Correct, although some administrators find it useful too
> Non GPL Modules are also restrited in the number of symbols they can use,
> this is to make it harder to derive work from the Linux Kernel with a ABI
> interface.
Non GPL modules are required not to be derivative works (a term of law).
The EXPORT_SYMBOL information is merely advisory to help seperate
symbols. In many cases its purely historical as to whether a symbol is
marked _GPL or not.
If a work is derivative of another GPL work by any means then the GPL
applies to it. If it is not then the GPL has no power over it because
the GPL is a copyright based license. The law itself circumscribes the
power of such licenses and their reach.
And no doubt German law could be totally different.
Alan
next prev parent reply other threads:[~2005-09-05 16:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 16:33 [ANNOUNCE] DSFS Network Forensic File System for Linux Patches Jeff V. Merkey
2005-08-31 18:32 ` Rik van Riel
2005-08-31 17:27 ` Jeff V. Merkey
2005-08-31 18:58 ` Arjan van de Ven
2005-08-31 18:00 ` Jeff V. Merkey
2005-08-31 21:28 ` Valdis.Kletnieks
2005-08-31 20:23 ` Jeff V. Merkey
2005-08-31 20:27 ` Jeff V. Merkey
2005-08-31 23:22 ` Diego Calleja
2005-08-31 22:50 ` jmerkey
2005-09-01 0:36 ` Bernd Eckenfels
2005-09-01 0:33 ` Bernd Eckenfels
2005-09-01 0:56 ` jmerkey
2005-09-01 1:44 ` jmerkey
[not found] ` <67029b1705083120142c0c1dea@mail.gmail.com>
2005-09-01 3:19 ` Zhou Yingchao
2005-09-01 7:12 ` Lincoln Dale
2005-09-01 7:45 ` Vojtech Pavlik
2005-09-01 10:23 ` Alan Cox
2005-09-01 8:28 ` Bernd Petrovitsch
2005-09-01 10:15 ` Alan Cox
2005-09-03 21:26 ` Bernd Eckenfels
2005-09-04 8:45 ` Alan Cox [this message]
2005-09-05 20:19 ` Bernd Eckenfels
2005-08-31 21:49 ` Jose Luis Domingo Lopez
2005-09-01 21:11 ` Alistair John Strachan
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=1125823531.23858.16.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ecki@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
/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