IEEE 1394 SBP-2 pseudo driver
Quoted 17 lines
From: Mark Garlanger [mailto:[email protected]]
Quoted 13 lines · Randy
Quoted 2 lines
From: Oliver Neukum [mailto:[email protected]]
...
Quoted 3 lines
USB calls a script named
/sbin/hotplugfor every event. The interface might be extended.Yes, the idea for
/sbin/hotplugis 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).
Quoted 4 lines
Quoted 1 line
~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
[email protected]
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 4 lines · Randy
BTW, this should probably be discussed on the new linux-hotplug mailing list [copied there, altho its archive is not yet happening].
There is an archive happening at
http://marc.theaimsgroup.com/?l=linux-hotplug-devel&r=1&w=2
which seems to be much more responsive and easier to use than the default SourceForge ones.
greg k-h
Signature · 6 lines
greg@(kroah|wirex).com _______________________________________________ Linux-hotplug-devel mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 4 lines
Quoted 2 lines
Wouldn't there be a problem if /sbin was mounted
on the device that was just unplugged?I suppose it would be.
I think Linus described that as a user error case ... there are a LOT of ways you can break system startup.
For example, if "/sbin/init" or "/sbin/modprobe" went away, similar bad things would happen.
I think Randy's got it right:
Quoted 8 lines
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.
Likely it should ... including conventions for how to extend the basic /sbin/hotplug functionality. The convention that's been discussed so far involves /etc/hotplug scripts; a SCSI hotplug agent would be "/etc/hotplug/scsi.agent", and could be updated independently from agents for USB, PCI, and so forth.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list
[email protected]
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel