From: Rusty Russell <rusty@rustcorp.com.au>
To: Marc Pignat <marc.pignat@hevs.ch>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Tom Horsley <tom.horsley@ccur.com>,
linux-kernel@vger.kernel.org,
Jon Masters <jonathan@jonmasters.org>
Subject: Re: module parameters versus kernel command line
Date: Sat, 5 Apr 2008 08:29:00 +1000 [thread overview]
Message-ID: <200804050829.00418.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200804041345.38482.marc.pignat@hevs.ch>
On Friday 04 April 2008 21:45:37 Marc Pignat wrote:
> On Friday 04 April 2008, Rusty Russell wrote:
> ...
>
> > The second is that users might be surprised when they take
> > the 'usbcore.blinkenlights' line out of their modprobe config file and it
> > still applies. Most users use everything-is-a-module distributions.
>
> Why don't do it in user space (let insmod/modprobe parse /proc/cmdline)?
> 1. Users won't be surprised after looking at the new man pages:)
> 2. it will work with older kernel
>
> The warning problem is more complicated to fix.
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.
The best bit about this idea: it's now Jon's problem :)
Cheers,
Rusty.
next prev parent reply other threads:[~2008-04-04 22:29 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 [this message]
2008-04-05 22:54 ` Tom Horsley
2008-04-06 3:08 ` Rusty Russell
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=200804050829.00418.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.