"bash: /dev/null: Permission denied" on Ubuntu Login...
UbuntuThis forum is for the discussion of Ubuntu Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The permissions on /dev/null are indeed set to 0600 (for whatever reason) and running a "sudo chmod 666 /dev/null" rectifies this problem. However, upon rebooting, the perms on /dev/null return to 0600. I am having this problem on another one of my Ubuntu boxen and I've no clue what I did to prompt it. My only guess was a system update.
Yeah, changing the permissions via /etc/rc.local was what I ultimately ended up doing shortly after posting the original thread. It works but, like others here, I would still like to know why this is happening in the first place. It's happened on 2 out of 3 of my Ubuntu machines (and I "treat" them all alike--I didn't do anything special to the 2 that gave me problems), and it's obviously happening to others.
I should probably file a bug report but I don't know how...