From: Alex Buell <alex.buell@munted.org.uk>
To: Michael Tokarev <mjt@tls.msk.ru>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Unused modules in 2.6.x
Date: Thu, 26 Feb 2009 10:29:39 +0000 [thread overview]
Message-ID: <20090226102939.42c92d34@lithium.local.net> (raw)
In-Reply-To: <49A59082.5040209@msgid.tls.msk.ru>
On Wed, 25 Feb 2009 21:40:02 +0300, I waved a wand and this message
magically appears in front of Michael Tokarev:
> > Perhaps I missed something when the 2.6.x kernels got started a few
> > years back, but why is it not possible for unused modules to be
> > automatically unloaded anymore i.e with rmmod -a? I remember being
> > able to do that with the 2.2.x and 2.4.x series a long time ago.
>
> It's a pure userspace question now. Well, almost, except of the
> single bit which were kept before 2.6 for each module - if it
> was loaded with -k flag (auto-unload) or not.
Thanks for that, I'll see if loading modules with -k still works in
2.6.x.
> Better question to ask, IMHO, is why network drivers don't gets
> referenced properly as all other drivers are. Because right now
> they're unused even if the network interfaces are up-n-running,
> and rmmod'ing a seemingly unused module will cause that particular
> interface to be removed too...
I'd have thought that hotplugging i.e. plug in an USB device in this
case would load the modules as and when required.
If the interface is up, then it shouldn't have to be unloaded, I think.
I know I could just hack my initrds to remove any modules that I don't
want loaded at bootup but surely... :-D
--
http://www.munted.org.uk
Fearsome grindings.
next prev parent reply other threads:[~2009-02-26 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 17:52 Alex Buell
2009-02-25 18:40 ` Michael Tokarev
2009-02-26 10:29 ` Alex Buell [this message]
2009-02-26 14:48 ` Lennart Sorensen
2009-02-25 19:28 ` Greg KH
2009-02-26 10:30 ` Alex Buell
2009-02-28 12:49 ` Stefan Richter
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=20090226102939.42c92d34@lithium.local.net \
--to=alex.buell@munted.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.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
all inboxes | Powered by JetHome®