From: Mike Castle <dalgoda@ix.netcom.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: modprobe problem with block-major-11
Date: Thu, 25 Oct 2001 09:39:05 -0700 [thread overview]
Message-ID: <20011025093904.C24125@thune.mrc-home.com> (raw)
In-Reply-To: <27036.1004015036@ocs3.intra.ocs.com.au>
On Thu, Oct 25, 2001 at 11:03:56PM +1000, Keith Owens wrote:
> The problem is caused by a bash "feature", it was added in bash 2.01.
Gotcha. I take it you've seen this before then? :->
I didn't see any mention of this the docs. Would it be worth while to add
what you just wrote to a PROBLEMS file?
> Workaround: Replace
> pre-install foo modprobe bar
> with
> before foo bar
Will do.
> That does all the work internally without using the system() function
> and falling foul of the bash feature. It is also faster and it lets
> modprobe maintain the chain of modules for unload.
>
> BTW, users can never run rmmod, only root can do that.
Right. But it IS with root that rmmod -a is failing.
Maybe I'll get lucky and it will magically start working when I switch to
the above?
Appreciate your help!
mrc
--
Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
next prev parent reply other threads:[~2001-10-25 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 4:53 Mike Castle
2001-10-25 5:51 ` Keith Owens
2001-10-25 7:52 ` Mike Castle
2001-10-25 13:03 ` Keith Owens
2001-10-25 16:39 ` Mike Castle [this message]
2001-10-25 18:20 ` Mike Castle
2001-10-25 18:51 ` Mike Castle
2001-10-25 8:09 ` Mike Castle
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=20011025093904.C24125@thune.mrc-home.com \
--to=dalgoda@ix.netcom.com \
--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®