linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: linux-kernel@vger.kernel.org, mru@users.sourceforge.net
Cc: nico-kernel@schottelius.org
Subject: Re: fun or real: proc interface for module handling?
Date: Thu, 31 Jul 2003 14:51:00 +0100	[thread overview]
Message-ID: <200307311351.h6VDp0w3000146@81-2-122-30.bradfords.org.uk> (raw)

> > I was just joking around here, but what do you think about this idea:
> >
> > A proc interface for module handling:
> >    /proc/mods/
> >    /proc/mods/<module-name>/<link-to-the-modules-use-us>
> >
> > So we could try to load a module with
> >    mkdir /proc/mods/ipv6
> > and remove it and every module which uses us with
> >    rm -r /proc/mods/ipv6
>
> So far, so good.
>
> > Modul options could be passed my
> >    echo "psmouse_noext=3D1" > /proc/mods/psmouse/options
> > which would also make it possible to change module options while runn=
> ing..
>
> 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...

Or you could just cause the module to be unloaded and reloaded
whenever options changed.

Not that I like this idea anyway, but then I don't use modules :-).

John.

             reply	other threads:[~2003-07-31 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 13:51 John Bradford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-01 13:54 fun or real: proc interface for module handling? Downing, Thomas
2003-07-31 12:12 Nico Schottelius
2003-07-31 12:34 ` Måns Rullgård
2003-07-31 13:03   ` Gábor Lénárt
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

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=200307311351.h6VDp0w3000146@81-2-122-30.bradfords.org.uk \
    --to=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@users.sourceforge.net \
    --cc=nico-kernel@schottelius.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;
as well as URLs for NNTP newsgroup(s).