steve crosby wrote:
From udev-047, udevd is capable of handling hotplug events from
modules, as well as devices, and knows to call the appropriate hotplug
rc script related to the module. (at module load, a hotplug event is
generated by the kernel, and calls whatever is defined as the hotplug
handler).
So it goes:
kernel (hotplug event) -> udevsend (hotplug handler) -> udevd -> hotplug
script (loads module which in turn populates /sys) -> udev (creates
device node)
Is that right? If so, how does udevd know it has to load a module? I'm
presuming it's because `udevsend' has already walked the /sys tree and
not found any relevant entries, so sets a flag telling udevd that it
doesn't know what the device is. A trivial grep for 'module' and
'hotplug' in the udev tarball doesn't shed enough light on this for me :(
Cheers,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
