All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel@schottelius.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: scholz@wdt.de
Subject: fun or real: proc interface for module handling?
Date: Thu, 31 Jul 2003 14:12:48 +0200	[thread overview]
Message-ID: <20030731121248.GQ264@schottelius.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

Hello!

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

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..

It's just an idea, perhaps someone likes this..
perhaps if there is enough feedback I even could think about
implementing it.


Greetings'

Nico

ps: please CC, the majordomo isn't answering my subscribe requests..

-- 
echo God bless America | sed 's/.*\(A.*\)$/Why \1?/'
pgp: new id: 0x8D0E27A4 | ftp.schottelius.org/pub/familiy/nico/pgp-key.new

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-07-31 12:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 12:12 Nico Schottelius [this message]
2003-07-31 12:34 ` fun or real: proc interface for module handling? 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
  -- strict thread matches above, loose matches on Subject: below --
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=20030731121248.GQ264@schottelius.org \
    --to=nico-kernel@schottelius.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scholz@wdt.de \
    /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.