Re: New hotplug interface is not working right for me

[Kay Sievers <kay.sievers@vrfy.org>]

On Mon, 2005-03-14 at 17:06 +0000, Darren Salt wrote:
> I demand that Kay Sievers may or may not have written...
> 
> [snip]
> > If the hotplug helper in /proc/sys/kernel/hotplug is set to /sbin/udevsend,
> > what all major distributions seems to do today,
> 
> FWIW, it's currently /sbin/hotplug here (sarge).

If you use a recent udev version, udevsend/udevd can manage the whole
hotplug handling by taking over the kernel spawned event process.

udev will first wait for sysfs to populate, create the node and then
execute the hotplug scripts. This way your scripts will not need to wait
for sysfs to show up and the name of the device node in in the
environment as DEVNAME.

The kernel events have a sequence number and udevd will reorder the
events. That way the scripts in /etc/hotplug.d/ will be executed in the
right order. It also cares about the serialization of events they belong
to the same device sequence. Your hotplug hooks can be sure that the
event for /dev/hda has completely finished before the event
for /dev/hda1 is executed.

This solves the problem to implement the complex logic for every hotplug
consumer again and again. As an example, the latest HAL version depends
on that and cannot work without udev's managed hotplug events.

Kay



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel