From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: rawhide hotplug broken
Date: Wed, 11 Apr 2001 01:11:06 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98695154931454@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98692454026185@msgid-missing>
> > Despite what Trond said (in a separate email on this thread), it
> > does more than just load modules; it also mounts "usbdevfs" at
> > the _right_ time (before USB host controller modules load)
>
> We do that.
Good to know -- the last version I looked at didn't work that way.
> The reason cold-plugging doesn't work with this because
> the fs isn't read-write at the time. So in our current package,
> hotplug actually waits around for a while for the root fs to
> become read-write. It's not the most elegant solution, but
> it was the quickest to code at the time.
Hmm, that'd explain the original problem:
- Using hotplug scripts old enough that they demand
that /tmp be writable ... so the pure bash version of
hotplugging won't work;
- Not having "usbmodules", so the bash code is the
only option.
Yes, that was an old bug in the hotplug scripts, now
fixed.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-04-11 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 17:41 rawhide hotplug broken Jack Howarth
2001-04-10 18:50 ` Trond Eivind Glomsrød
2001-04-10 18:57 ` Jack Howarth
2001-04-10 20:21 ` Bill Nottingham
2001-04-11 0:39 ` David Brownell
2001-04-11 1:03 ` Bill Nottingham
2001-04-11 1:11 ` David Brownell [this message]
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=marc-linux-hotplug-98695154931454@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).