Starting /etc/init.d/udev can take more than a few seconds to finish. When it fails it remains silent and often hangs - the reasons are usually beyond its control. Currently the only way to find out what failed is to start the system interactively and/or figuring out what went wrong by reading dmesg output. I think adding --verbose to the `udevadm trigger' calls in populate_dev() might help resolve issues much easier.
udevadm trigger --verbose is /really/ verbose - it prints out a complete list, sadly.
You are correct, adding --verbose by default to the udevadm trigger commands would make for a very verbose boot. What I could do is give you a way to add it yourself if you want it, for example a variable like trigger_extra_opts in /etc/conf.d/udev-trigger which would then be passed to the udevadm trigger commands. By default it would be empty because of the amount of output the --verbose option would generate. What do you think about this idea?
Closing due to lack of response.
