Recently, /sbin/udevd was moved to /usr/lib64/systemd/systemd-udevd on my system. My system then crashed, and upon reboot was unbootable because all the init scripts still pointed to /sbin/udevd. /sbin/udevd should be symlinked to the new location of 'systemd-udevd'. Doing so allowed my system to boot again. After a sufficient transition period, this symlink can be dropped.
Why don't you simply update the udev start script in /etc/init.d via etc-update command?
I have now fixed it. The problem is that my system crashed between the two. I just don't see any purpose for making the transition in an unsafe state that can render a system unbootable if it can be made safe with a simple symlink.
Updating things like udev & openrc, then rebooting before merging new configs, has always been a recipe for disaster. Don't do that.
Of course, I wouldn't do it on purpose. But if it's going to be a part of a frequently multi-hundred package update, you have to expect that there's a chance of an unintended reboot. Are you saying that a symlink isn't worth the safety? I could come up with several other ways to make this work well. You could force/reccomend these changes to be emerged seperatly so that their config changes will be merged quickly. You could have a setup similar to etc-update that switches both at once. You could decide that some config changes should be auto-merged. But I think the symlink is easy and safe.
I can do that, but running the newer udev with older udev init scripts hasn't been tested, so I can't be sure you would gain anything from running it that way.
Portage does print a message for configuration update. Miss anything boot related and you are likely screwed. Nothing to do here far as I can see.
*** This bug has been marked as a duplicate of bug 408891 ***
