Summary: | After system update udev faild to start | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | lexx <lexxkind> |
Component: | [OLD] Core system | Assignee: | udev maintainers <udev-bugs> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | a.nielsen, pchrist, savage.mephisto |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
lexx
2008-12-23 16:28:51 UTC
What were the udev/openrc/sysvinit versions when booting failed ? Did you run etc-update after emerging ? *** Bug 252305 has been marked as a duplicate of this bug. *** (In reply to comment #1) > What were the udev/openrc/sysvinit versions when booting failed ? > > Did you run etc-update after emerging ? > Please verify if you have run etc-update or not. Any progress here? (In reply to comment #4) > Any progress here? > I'm not the OP but I can verify that I have updated incoming config files as asked in previous post. In my case I used cfg-update but still there are no more files to update and on restart udev still fails to start. should there be something uncommented in /etc/conf.d/udev? In my case its only comments. After bootup, with udev having failed to start... no cmdline tools are found, no PATHS are set etc so nothing can really be done short of booting off an install img or livecd and chrooting. But what to do? Attempting to start udev manually raises the original error reported by OP. Which udev version do you use? udev-135-r2 does not use addon code. So either you have an older version or did not update the cponfig-files/init-scripts properly. After emerge udev run etc-update and update your config files in /etc/init.d/ We cannot do anything here without further information. Just came across this same issue, same error and symptoms. Running etc-update and updating all the files related to udev fixed the problem. |