From: "Gábor Lénárt" <lgb@lgb.hu>
To: M?ns Rullg?rd <mru@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fun or real: proc interface for module handling?
Date: Thu, 31 Jul 2003 15:03:38 +0200 [thread overview]
Message-ID: <20030731130338.GB23570@vega.digitel2002.hu> (raw)
In-Reply-To: <yw1xptjqub7q.fsf@users.sourceforge.net>
On Thu, Jul 31, 2003 at 02:34:01PM +0200, M?ns Rullg?rd wrote:
> > Modul options could be passed my
> > echo "psmouse_noext=1" > /proc/mods/psmouse/options
> > which would also make it possible to change module options while running..
>
> How would options be passed when loading? Some modules require that
> to load properly. Also, there are lots of options that can't be
> changed after loading. To enable this, I believe the whole option
> handling would need to be modified substantially. Instead of just
> storing the values in static variables, there would have to be some
> means of telling the module that its options changed. Then there's
> the task of hacking all modules to support this...
Interesting :)
Maybe, it should cause no action to "mkdir /proc/mods/ipv6", nor echo
"psmouse_noext=1" > /proc/mods/psmouse/options
_just_ "collecting" parameters by kernel, then eg creating a file
/proc/mods/ipv6/load should cause to load the module. Of course there can be
code to handle "on-the-fly" parameter change, but maybe this can be
considered as optimal, and it should be not a must a module to support this
...
- Gábor (larta'H)
next prev parent reply other threads:[~2003-07-31 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 12:12 fun or real: proc interface for module handling? Nico Schottelius
2003-07-31 12:34 ` Måns Rullgård
2003-07-31 13:03 ` Gábor Lénárt [this message]
2003-07-31 23:15 ` jw schultz
2003-08-01 5:55 ` Stuart Longland
2003-07-31 13:13 ` Yaroslav Rastrigin
2003-07-31 13:29 ` Nico Schottelius
2003-07-31 23:59 ` Grant Miner
2003-07-31 13:51 John Bradford
2003-08-01 13:54 Downing, Thomas
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=20030731130338.GB23570@vega.digitel2002.hu \
--to=lgb@lgb.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@users.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).