From: Stephen Hemminger <shemminger@osdl.org>
To: Alex Goddard <agoddard@purdue.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4, or what I still don't quite like about the new stable branch
Date: Wed, 17 Mar 2004 14:40:38 -0800 [thread overview]
Message-ID: <20040317144038.533c9150@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0403171709000.4288@dust.p68.rivermarket.wintek.com>
On Wed, 17 Mar 2004 17:27:50 -0500 (EST)
Alex Goddard <agoddard@purdue.edu> wrote:
> On Wed, 17 Mar 2004, Helge Hafting wrote:
>
> > Alex Goddard wrote:
> > [...]
> > >
> > > Safe module unloading is a very difficult problem. So much so that
> > > disallowing unloading modules completely has been discussed in the past.
> > > Digging around an lkml archive for more info on why module unloading is
> > > inherently problematic, and not at all easy to do (well, not at all easy
The problem for must users of earlier versions of linux is the definition of
safe changed. Safe now means you can remove the module without crashing
the kernel. Safe used to mean that nothing could possible be using the code.
Sort of like difference between NFS hard and soft mount.
A bigger issue is that there seems to be a whole set of smaller distro's and
people who write their own startup scripts that became addicted to the old behaviour.
I wish all the distro's would get rid of explicit modprobe and rmmod's in startup
scripts.
next prev parent reply other threads:[~2004-03-17 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 18:27 Marek Szuba
2004-03-13 18:44 ` Grzegorz Kulewski
2004-03-16 0:17 ` Peter Williams
2004-03-13 21:54 ` Alex Goddard
[not found] ` <4058097F.4070606@aitel.hist.no>
2004-03-17 22:27 ` Alex Goddard
2004-03-17 22:40 ` Stephen Hemminger [this message]
2004-03-13 22:21 ` Sam Ravnborg
2004-03-17 23:15 ` James Simmons
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=20040317144038.533c9150@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=agoddard@purdue.edu \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®