Re: udevsynthesize as a udevstart+coldplug replacement

[Christian Zoz <zoz@suse.de>]

On Wed, Aug 24, Marco d'Itri wrote:
> On Aug 24, Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > > What about a new udevcontrol parameter which makes it block until the
> > > udevd is done?
> > What state is "udevd is done"? No event in the queue?
> Unless you can think about something smarter, yes.

No UDEV_SYNTHESIZE event in the queue.

> > > This way if needed it could be run in a different init
> > > script to allow parallel processing at boot time.
> > Hmm, what do you mean? Who waits for whom?
> multiple init scripts would depend on the udev-done (or something like
> this) init script, which will not terminale until udevcontrol will.
> This way other init scripts would be able to continue working without
> needing to wait for udev.
> Or maybe it's not worth the effort, because they would need to use
> /some/ device node anyway.

Why not make the init scripts wait individually for whatever they need?

-- 

ciao, christian

睡眠不足はいい仕事の敵だ。


-------------------------------------------------------
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