From: "Dunlap, Randy" <randy.dunlap@intel.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: IEEE 1394 SBP-2 pseudo driver
Date: Mon, 08 Jan 2001 16:48:45 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97897252601687@msgid-missing> (raw)
> From: Mark Garlanger [mailto:garlangr@directlink.net]
>
> "Dunlap, Randy" wrote:
>
> > > From: Oliver Neukum [mailto:Oliver.Neukum@lrz.uni-muenchen.de]
> > >
> > ...
> > >
> > > USB calls a script named /sbin/hotplug for every event.
> > > The interface might be extended.
> >
> > Yes, the idea for /sbin/hotplug is to use it for any/all
> > buses that need/want to add hotplug support.
> > It began with USB but has had some updates for cardbus
> > already. And it has Linus's support (since he was in on
> > its definition).
> >
> > ~Randy
>
> Wouldn't there be a problem if /sbin was mounted
> on the device that was just unplugged?
I suppose it would be. It's not nice to unplug /sbin, is it?
(checking FHS 2.1)
Or if someone does need to unplug/replug /sbin, should there
be a mirror (or soft-link) of it?
The actual file name used for the hotplug program (script)
is stored in /proc/sys/kernel/hotplug, so changing that
during /sbin unplug/replug is also an option.
Looks to me like /sbin is a good place for it according to
FHS 2.1. FHS 2.2 is being updated now, but I don't see any
changes in it to address hotplug.
I doubt that FHS took hot unplug/plug into account.
BTW, this should probably be discussed on the new
linux-hotplug mailing list [copied there, altho its
archive is not yet happening].
~Randy
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2001-01-08 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 16:48 Dunlap, Randy [this message]
2001-01-08 18:31 ` IEEE 1394 SBP-2 pseudo driver Greg KH
2001-01-08 21:55 ` David Brownell
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-97897252601687@msgid-missing \
--to=randy.dunlap@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.