Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Having an odd boot message with Ubuntu 10.04. I've had it since I first installed Ubuntu a few months back and I am getting tired of it slowing down my boot up time.
No luck on the Ubuntu forums or bug reports; no one seems to know what to do.
Quote:
udevd-work [332] open /dev/null failed no such file or directory
Suggestion in the thread that it is fixed in 10.10 and only an issue in 10.04.
My first thought even before seeing the bug was this is a timing thing. Your udevd-work is trying to do something before /dev/null is created. You might want to check your udev rules to see the ones that deal with "null" (not just /dev/null). I don't have an Ubuntu box so can't see the way Ubuntu creates null device in its rules.
My first thought even before seeing the bug was this is a timing thing. Your udevd-work is trying to do something before /dev/null is created. You might want to check your udev rules to see the ones that deal with "null" (not just /dev/null). I don't have an Ubuntu box so can't see the way Ubuntu creates null device in its rules.
In /etc/udev on RHEL/CentOS - not sure if they are in the same location on Ubuntu. There is a man page on RHEL/CentOS so may be on Ubuntu as well - type "man udev" to see if there is one then read what it has to say if so.
In case it helps: Slackware for one, is now putting udev rules in /lib/udev/rules.d so if yours aren't in /etc/udev/rules.d or similar then have a look in /lib/udev instead. I haven't got Ubuntu installed, or I'd have a look.
Interestingly enough the problem has resolved itself (for now) with no effort on my part. I'll go an a udev rules hunt anyway in case it creeps up again.
My only complaint now is screen resolution during boot up. For a different thread, I suppose...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
