From: tomas szepe <kala@pinerecords.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: The tainted message
Date: Tue, 30 Apr 2002 01:53:31 +0200 [thread overview]
Message-ID: <20020429235330.GA27307@louise.pinerecords.com> (raw)
In-Reply-To: <20020429192107.GA26369@louise.pinerecords.com> <26170.1020121574@ocs3.intra.ocs.com.au>
> Nobody can agree on the warning text. Anything less than the full
> kernel FAQ entry is incomplete.
Hey, no need for sarcasm here; I don't think the four lines could offend
anyone, being merely a different solution proposal. Yours is pretty good
too.
> Solution:
>
> modutils 2.4.16 says
>
> Warning: loading <module> will taint the kernel. Reason <reason>
> See <TAINT_URL> for information on tainted modules
> Module loaded, with warnings
>
> Printing 'Module loaded, with warnings' makes it clear that the
> module has been loaded. TAINT_URL defaults to lkml FAQ. Vendors can
> ship modutils with a TAINT_URL that points to their support policy.
Neat!
T.
next prev parent reply other threads:[~2002-04-29 23:53 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
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 [this message]
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=20020429235330.GA27307@louise.pinerecords.com \
--to=kala@pinerecords.com \
--cc=kaos@ocs.com.au \
--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®