PDA

View Full Version : [ubuntu] [SOLVED] Problem with terminal and /dev/null error



alienexplorers
May 19th, 2008, 08:23 AM
When I start up terminal I get a error for about 5 seconds before it lets me run anything. I have included a picture of the error. Any help would be appreciated.

sdennie
May 19th, 2008, 08:28 AM
What are the permissions on /dev/null?



ls -l /dev/null

alienexplorers
May 19th, 2008, 08:44 AM
crw-rw-rw- 1 terminator terminator 2, 2 2008-05-19 02:58 /dev/null

have also tried root root and that caused the error too.

sdennie
May 19th, 2008, 08:50 AM
I have no idea how the permissions got changed but, you could try the following:



sudo chown root:root /dev/null

alienexplorers
May 19th, 2008, 08:54 AM
crw-rw-rw- 1 root root 2, 2 2008-05-19 02:58 /dev/null

Still getting the same error about bash and /dev/null

sdennie
May 19th, 2008, 09:08 AM
I would try the following (it looks scary but, check "man null"):



sudo rm /dev/null
sudo mknod -m 666 /dev/null c 1 3
sudo chown root:root /dev/null

alienexplorers
May 19th, 2008, 09:20 AM
Well that fixed the problem. Many, many thanks.

sdennie
May 19th, 2008, 09:29 AM
Glad it worked. I'm still not sure how your /dev/null got into that state so it may revert. It's possible that you have some errant udev rule that's making it do that. You could check with:



grep terminator /etc/udev/rules.d/*
grep null /etc/udev/rules.d/*


The last command should return one line in 40-basic-permissions.rules

alienexplorers
May 19th, 2008, 09:39 AM
grep null /etc/udev/rules.d* gives the following output:

/etc/udev/rules.d/40-basic-permissions.rules:KERNEL=="null", MODE="0666"
grep terminator /etc/udev/rules.d* gives no output.

sdennie
May 19th, 2008, 09:41 AM
That looks correct. If upon reboot or starting an app, you start to get the /dev/null errors again, it would be interesting to know what happened to get /dev/null in that state.

alienexplorers
May 19th, 2008, 09:44 AM
I wish I knew what got /dev/null in that state to start with. All I was doing is scanning threw the Ubuntu forums and went to try something in terminal and got that error before typing anything.