From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dunlap, Randy" Date: Mon, 08 Jan 2001 16:48:45 +0000 Subject: RE: IEEE 1394 SBP-2 pseudo driver Message-Id: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org > 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