Pozsar Balazs wrote:
> I still think, the best solution would be:
>  - udevd itself triggers all the uevents
>  - when it finished processing all these events, only then daemonizes 
>    itself.
> So the udevd startup script could be nothing more than:
>   udevd --daemon
> 
> Nice daemons always have this kind of behavior: they does not fork 
> and return immediately, but return if the daemon successfully started 
> and initalized itself. For a good example, see hald.
> 
> 

/signed

you may test:
ftp://people.redhat.com/harald/udev/udev-075-5.src.rpm
which has the attached patch :)