You are not logged in.
Pages: 1
Topic closed
Hi All. After today's latest kernel update to kernel26 2.6.32.4-1 when I'm starting the system during boot suddenly appears:
error binding control socket, seems udev is already running
After that the system boots normally. Does anyone experienced such an issue and what does it mean? THNX
Offline
Same here . Also before this warning, it prints udevd starts, along with initramfs. I have not noticed this before.
Thanks
Jithin
Offline
http://bbs.archlinux.org/viewtopic.php?id=88936
Please search before posting.
Offline
I'm sorry for duplicating the subject but one week has passed and the problem still exists and I didn't find the solution. I hoped that yesterday's kernel update will fix the problem but "error binding control socket, seems udev is already running" appears during the boot process. I know that it's harmless but I would like to do something with this error.
Offline
Yeah, it's harmless, it will go away when the newer versions of mkinitcpio are released. Mailing list says just ignore it.
Offline
Nixxx - clearly you didn't read the link I posted above. My post in that thread describes a short-term workaround that you can use until the devs fix the bug.
Next time you ask for help and get a response, can you please read it?
If the above is too much for you, here's another workaround - stop watching your system booting.
Offline
Profjim - mkinitcpio updated to 0.5.30-1 and the error still appears.
tomk - don't worry I've read your post.
Offline
As tomk pointed out, there is another topic covering this, so if there's any questions to be raised or if you want to discuss this issue further, let's centralise our efforts in that topic instead of opening new ones.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Pages: 1
Topic closed