From: "Morgan Collins [Ax0n]" <sirmorcant@morcant.org>
To: linux-kernel@vger.kernel.org
Subject: Tainted Modules Help Notices
Date: Wed, 10 Oct 2001 01:06:03 -0700 (PDT) [thread overview]
Message-ID: <32879.24.255.76.12.1002701163.squirrel@webmail.morcant.org> (raw)
After compiling 2.4.11 I noticed modprobe picking up some of the tainted modules that
were marked in the update.
What surprised me was the PPP compression modules, I didn't use PPP in 2.4.10 so maybe
the notice was there in 2.4.10, but I didn't use them so I didn't see it. I shouldn't have
been surprised, but I was. BSD compression, BSD license... doh... :>
I do however at times use the nls modules, and I see a great deal of them are BSD-NAC
licensed. It's also nice to have ipchains_core laying around for compatibility at times as
well. If I had known this at compile time I would have opted not to compile them, as
modules or otherwise. Knowing now that there are modules in the kernel build tree that are
not GPLed, and since I don't know which ones, I will grep for MODULE_LICENSE first from
now on.
After this discovery, I would like to ask opinions on including licensing terms in
item/module help files. It would be very convient if under dpt_i2o help it said that it
was licensed under BSD-NAC.
--
Morgan Collins [Ax0n] http://sirmorcant.morcant.org
Software is something like a machine, and something like mathematics, and something like
language, and something like thought, and art, and information.... but software is not in
fact any of those other things.
next reply other threads:[~2001-10-10 8:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 8:06 Morgan Collins [Ax0n] [this message]
2001-10-10 8:20 ` David Woodhouse
2001-10-10 8:24 ` Morgan Collins [Ax0n]
2001-10-10 8:31 ` David Woodhouse
2001-10-10 13:50 ` Keith Owens
2001-10-10 13:59 ` Alexander Viro
2001-10-10 14:01 ` Keith Owens
2001-10-10 17:30 ` Alan Cox
2001-10-10 18:18 ` David Woodhouse
2001-10-10 20:06 ` Concerned Programmer
2001-10-10 20:28 ` Morgan Collins [Ax0n]
2001-10-10 21:28 ` Keith Owens
2001-10-10 22:03 ` Anthony DeRobertis
2001-10-11 7:27 ` David Woodhouse
2001-10-10 21:17 ` Alan Cox
2001-10-10 23:02 ` Juan Quintela
2001-10-10 23:28 ` Andreas Dilger
2001-10-10 22:29 ` Rob Landley
2001-10-11 2:48 ` 2.4.11 UDF Morgan Collins [Ax0n]
2001-10-11 3:26 ` Craig Whitmore
2001-10-11 8:50 ` Tainted Modules Help Notices Andreas Ferber
2001-10-11 9:25 ` Alan Cox
2001-10-11 9:35 ` Henning P. Schmiedehausen
2001-10-11 9:41 ` Pekka Pietikäinen
2001-10-11 9:48 ` Syed Mohammad Talha
2001-10-11 10:09 ` Concerned Programmer
2001-10-11 10:37 ` Alan Cox
2001-10-11 22:42 ` David Schwartz
2001-10-11 23:40 ` John Alvord
2001-10-12 1:12 ` David Schwartz
2001-10-12 1:32 ` Robert Love
2001-10-11 12:10 ` James Sutherland
2001-10-10 14:13 ` David Woodhouse
2001-10-10 14:18 ` Alexander Viro
2001-10-10 13:10 ` Alan Cox
2001-10-10 14:06 Bonds, Deanna
2001-10-10 14:24 ` Arjan van de Ven
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=32879.24.255.76.12.1002701163.squirrel@webmail.morcant.org \
--to=sirmorcant@morcant.org \
--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
all inboxes | Powered by JetHome®