Messages in this thread | | | Date | Thu, 3 Oct 2002 09:30:19 -0700 | From | Greg KH <> | Subject | Re: EVMS Submission for 2.5 |
| |
On Thu, Oct 03, 2002 at 12:21:13PM -0400, Alexander Viro wrote: > On Thu, 3 Oct 2002, Greg KH wrote: > > /sbin/hotplug already gets called for _every_ device that is added to > > the system as of 2.5.40, so you should probably use that as your > > userspace notifier event. If there's anything that the /sbin/hotplug > > call misses, that you need for evms, please let me know. > > We need it > a) early enough
Your initramfs patches will enable this to happen :)
> b) called for things like umem, etc. - random drivers built into > the tree and exporting several block devices.
All devices that have a "struct device" (which should be about everything these days, if not, please let me know), cause a /sbin/hotplug event to happen. This event says what type of device was added or removed, and includes the location of the device in the driverfs tree so that userspace can then determine what it wants to do with this device.
I'm working on adding a call to /sbin/hotplug when classes are registered with the kernel (like disk and other things that live in the class driverfs tree).
Is this enough information to do what you need?
thanks,
greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |