From: Rusty Russell <rusty@rustcorp.com.au>
To: Tom Horsley <tom.horsley@ccur.com>
Cc: Marc Pignat <marc.pignat@hevs.ch>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org,
Jon Masters <jonathan@jonmasters.org>
Subject: Re: module parameters versus kernel command line
Date: Sun, 6 Apr 2008 13:08:30 +1000 [thread overview]
Message-ID: <200804061308.30921.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080405185444.2c433673@tomh>
On Sunday 06 April 2008 08:54:44 Tom Horsley wrote:
> On Sat, 5 Apr 2008 08:29:00 +1000
>
> Rusty Russell <rusty@rustcorp.com.au> wrote:
> > I like this idea, and also have module tools ship with
> > a 'check-kernel-cmdline' tool which handles the warnings for unusable
> > cmdline params. Distributions can run this in their init scripts, and we
> > can remove the warning from the kernel.
>
> Or maybe not have the warning at all, after all, even if
> sillymodule.sillyarg=1 doesn't make sense when I booted, who's to say I
> can't download the source to sillymodule, compile it, and modprobe it after
> boot time :-).
I think it's worse not to have typo protection. Of course, our logs are so
noisy they might miss the warning anyway.
Rusty.
next prev parent reply other threads:[~2008-04-06 3:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 13:00 module parameters versus kernel command line Tom Horsley
2008-04-03 15:39 ` Randy Dunlap
2008-04-03 16:04 ` Tom Horsley
2008-04-03 16:14 ` Randy Dunlap
2008-04-03 23:09 ` Rusty Russell
2008-04-04 11:45 ` Marc Pignat
2008-04-04 22:29 ` Rusty Russell
2008-04-05 22:54 ` Tom Horsley
2008-04-06 3:08 ` Rusty Russell [this message]
2008-04-03 16:31 ` Chris Friesen
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=200804061308.30921.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.pignat@hevs.ch \
--cc=randy.dunlap@oracle.com \
--cc=tom.horsley@ccur.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.