> > 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: > 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 - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]
