From: Keith Owens <kaos@ocs.com.au>
To: Richard Thrapp <rthrapp@sbcglobal.net>
Cc: Francois Romieu <romieu@cogenit.fr>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: The tainted message
Date: Sun, 28 Apr 2002 10:33:56 +1000 [thread overview]
Message-ID: <31492.1019954036@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "27 Apr 2002 10:51:52 EST." <1019922717.8819.62.camel@wizard>
On 27 Apr 2002 10:51:52 -0500,
Richard Thrapp <rthrapp@sbcglobal.net> wrote:
>On Sat, 2002-04-27 at 07:08, Francois Romieu wrote:
>> Richard Thrapp <rthrapp@sbcglobal.net> :
>> [...]
>> > First of all, the current tainted message is not really useful.
>> > "Warning: Loading %s will taint the kernel..." isn't very informative at
>> > all. Most people don't know what it means to "taint the kernel". It's
>>
>> Add a reference to http://www.tux.org/lkml/#s1-18. An explanation is already
>> there.
>
>That doesn't fix the problem. The message is still wrong. A reference
>to an explanation only helps the people who can reach it immediately.
>Linux is also used on manufacturing floors (and several other places)
>where no network connections exist.
Those people can modify and ship a version of modutils that does not
issue the taint message. That makes it their problem, not ours. I
know of at least one embedded system distributer who is doing just
this.
If you want to ship binary only modules and you don't want your users
to question this, removal of the warning messages is your problem. GPL
allows anybody to change any messages they like as long as they supply
the changed source. I will not (cannot) stop people changing modutils
to defeat community expectations but I will not support them either.
next prev parent reply other threads:[~2002-04-28 0:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 4:51 Richard Thrapp
2002-04-27 7:50 ` arjan
2002-04-27 8:06 ` Enrico Demarin
2002-04-27 18:45 ` Alan Cox
2002-04-27 12:08 ` Francois Romieu
2002-04-27 15:51 ` Richard Thrapp
2002-04-27 17:02 ` was: " Francois Romieu
2002-04-28 0:33 ` Keith Owens [this message]
2002-04-27 15:20 ` Alan Cox
2002-04-27 14:27 ` Martin Dalecki
2002-04-27 18:41 ` Alan Cox
2002-04-27 16:03 ` Richard Thrapp
2002-04-27 16:28 ` Bob_Tracy
2002-04-27 16:57 ` Robert Love
2002-04-29 16:59 ` Brian Beattie
2002-04-29 17:15 ` tomas szepe
2002-04-29 17:43 ` Ian Molton
2002-04-29 17:41 ` Thomas 'Dent' Mirlacher
2002-04-29 18:16 ` Ian Molton
2002-04-29 18:14 ` tomas szepe
2002-04-29 17:42 ` tomas szepe
2002-04-29 19:11 ` John Alvord
2002-04-29 19:21 ` tomas szepe
2002-04-29 18:41 ` Sandy Harris
2002-04-29 20:00 ` tomas szepe
2002-04-29 23:06 ` Keith Owens
2002-04-29 23:53 ` tomas szepe
2002-04-30 13:37 ` john slee
2002-04-30 13:44 ` Keith Owens
2002-04-29 18:14 ` Christian Bornträger
2002-04-29 17:34 ` Sandy Harris
2002-04-27 19:22 ` Chris Abbey
2002-04-27 19:50 ` Alan Cox
2002-04-28 0:27 ` Keith Owens
2002-04-28 1:27 ` Richard Thrapp
2002-04-28 1:41 ` Keith Owens
2002-04-28 2:14 ` Richard Thrapp
2002-04-28 2:00 ` Alan Cox
2002-04-30 8:36 Martin Knoblauch
2002-05-02 7:35 Martin Knoblauch
2002-05-02 11:55 ` Keith Owens
2002-05-02 13:08 ` Martin Knoblauch
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=31492.1019954036@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@cogenit.fr \
--cc=rthrapp@sbcglobal.net \
/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®