From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Yann Dirson <ydirson@altern.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Generic modules documentation is outdated
Date: Fri, 19 Jul 2002 10:24:12 +0200 [thread overview]
Message-ID: <20020719082412.GA6490@tahoe.alcove-fr> (raw)
In-Reply-To: <20020718210259.GJ19580@bylbo.nowhere.earth>
On Thu, Jul 18, 2002 at 11:02:59PM +0200, Yann Dirson wrote:
> I dicovered that I could "echo 0 >
> /proc/sys/kernel/tainted"
>
> => is this reasonable ?
Yes, if you are smart enough to do this you could also edit the oops
report or even patch nvidia licence tag etc. It's just a help to
the kernel developers to sort out newbie bug reports, nothing more.
> => isn't there a mechanism that triggers a kernel log when "tainted" is set ?
> Any reason for not having one ?
There is no internal kernel function being called in order to
initialise this flag. insmod just sets the value of the symbol, it
doesn't call a kernel function which could make an entry into the logs.
However, insmod can and should IMHO syslog this.
> - In 2.4.18 I can't find any information about the modules licencing issues
> in Documentation/modules.txt (nor in Documentation/kmod.txt, but I don't
> feel this one would be the place for this, correct me if I'm wrong)
See Documentation/oops-tracing.txt and Documentation/sysctl/kernel.txt
(in 2.4.19-rc2 at least).
Stelian.
--
Stelian Pop <stelian.pop@fr.alcove.com>
Alcove - http://www.alcove.com
prev parent reply other threads:[~2002-07-19 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 21:22 oops with 2.4.18 and preempt patch, on SMP + ext3 machine Yann Dirson
2002-07-18 21:02 ` Generic modules documentation is outdated Yann Dirson
2002-07-18 22:48 ` Alan Cox
2002-07-18 23:17 ` Yann Dirson
2002-07-18 23:25 ` Yann Dirson
2002-07-18 23:04 ` Richard B. Johnson
2002-07-19 8:12 ` Stelian Pop
2002-07-23 6:56 ` Dual BSD/GPL [ was: Re: Generic modules documentation is outdated] Andrew Rodland
2002-07-22 12:25 ` Alan Cox
2002-07-19 8:24 ` Stelian Pop [this message]
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=20020719082412.GA6490@tahoe.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ydirson@altern.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®