Re: udevsynthesize as a udevstart+coldplug replacement

["Mika Penttilä" <mika.penttila@kolumbus.fi>]

Kay Sievers wrote:

>Here is "udevsynthesize" a possible replacement for the udevstart/coldplug
>combination we currently have. Usually very early in the boot process, it
>gets all available devices from sysfs and synthesizes the events these
>devices would have generated at creation time.
>The events are directly passed to the udevd daemom socket. udevd does all the
>work and runs all the events asynchronously. udevsynthesize itself does
>not read any udev rule.
>
>It scans block and class devices to create the the device nodes for already
>available devices, which obsoletes the run of udevstart.
>After that, it scans for bus devices, which events may load modules or
>configure the device. If the bus type is known, the usual bus-specific
>values are added to the event environment.
>
>With the "rules-in-daemon" patch, the whole udevstart/coldplug handling
>(700 events) takes less than a second CPU time on a 1.7Ghz laptop.
>
>A typical boot script would do:
>  prepare tmpfs on /dev
>  create /dev/null
>  start /sbin/udevd
>  disable /proc/sys/kernel/hotplug (the input layer is still broken and needs a kernel patch)
>  run /sbin/udevsynthesize
>
>Have fun,
>Kay
>  
>

What if udevd receives netlink messages and goes into "ignore unix 
socket" mode before/while synthesize?

--Mika



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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