From: Nico Schottelius <nico-kernel@schottelius.org>
To: Yaroslav Rastrigin <yarick@relex.ru>
Cc: Nico Schottelius <nico-kernel@schottelius.org>,
linux-kernel@vger.kernel.org
Subject: Re: fun or real: proc interface for module handling?
Date: Thu, 31 Jul 2003 15:29:00 +0200 [thread overview]
Message-ID: <20030731132900.GU264@schottelius.org> (raw)
In-Reply-To: <200307311713.24788.yarick@relex.ru>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Yaroslav Rastrigin [Thu, Jul 31, 2003 at 05:13:24PM +0400]:
> > 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
> >
>
> Well, this idea itsel is quite neat, and could sometimes save lots of time
> (esp. when dealing with serious modules' deps). I would like to propose
> slightly different appropach:
> cp /lib/modules/2.6.0-test2/kernel/drivers/somedriver.ko /proc/modtree
> [...]
sounds nice, too.
With this idea the kernel would get the code directly, which is very nice.
Nico
--
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 --]
next prev parent reply other threads:[~2003-07-31 13:30 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
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 [this message]
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=20030731132900.GU264@schottelius.org \
--to=nico-kernel@schottelius.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yarick@relex.ru \
/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).