From: Keith Owens <kaos@ocs.com.au>
To: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
Cc: Alan Cox <laughing@shared-source.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.12-ac5
Date: Mon, 22 Oct 2001 18:05:46 +1000 [thread overview]
Message-ID: <23534.1003737946@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 21 Oct 2001 23:41:10 CST." <20011021234110.A4193@zed.dlitz.net>
On Sun, 21 Oct 2001 23:41:10 -0600,
"Dwayne C. Litzenberger" <dlitz@dlitz.net> wrote:
>Alan, is this normal?
>
>zed:~# cat /proc/sys/kernel/tainted
>1
>zed:~# echo "0" >/proc/sys/kernel/tainted
>zed:~# cat /proc/sys/kernel/tainted
>0
I decided against adding special code to sysctl for the taint flag so
yes, you can clear it. There is no point in adding special code for
the taint sysctl, it is even easier to remove the taint message from
the log before submitting.
As AC has said (several times) tainting is not foolproof, it is to help
triage bug reports from people who don't submit complete information.
Those users who know enough to lie are also unlikely to submit bug
reports. Tainting is to help beginners.
next prev parent reply other threads:[~2001-10-22 8:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 23:45 Linux 2.4.12-ac5 Alan Cox
2001-10-22 0:20 ` Udo A. Steinberg
2001-10-22 0:54 ` Dave Jones
2001-10-22 1:19 ` Udo A. Steinberg
2001-10-22 1:26 ` Robert Love
2001-10-22 8:05 ` Alan Cox
2001-10-22 8:03 ` Robert Love
2001-10-22 8:15 ` Alan Cox
2001-10-22 1:48 ` Dave Jones
2001-10-22 5:41 ` Dwayne C. Litzenberger
2001-10-22 7:56 ` Alan Cox
2001-10-22 8:05 ` Keith Owens [this message]
2001-10-23 6:57 ` Linux 2.4.12-ac5 typo Gregory Ade
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=23534.1003737946@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=dlitz@dlitz.net \
--cc=laughing@shared-source.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