lkml.org 
[lkml]   [2002]   [Apr]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: The tainted message
Date
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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:25    [W:0.149 / U:1.864 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site