[SOLVED]-bash: /dev/null: Permission denied

p4l4cl][n · 2012-06-06 13:54:01

Hi,
After update and reboot I now got -bash: /dev/null: Permission denied each time I log in... /dev/null is after reboot set to 600, I can chmod it to 666, but how can I make it persist?

Any help will be appreciated (^_^)

Thanks a lot

Last edited by p4l4cl][n (2012-06-06 14:57:07)

Gcool · 2012-06-06 14:07:05

Can you still login as root?

Check which shell is configured for your specific user (grep <youruser> /etc/passwd). If this is set to /dev/null for whatever reason, you can use "chsh" to change it (to /bin/bash for example).

p4l4cl][n · 2012-06-06 14:09:18

Oh, I propably did not say it right (I am not a native speaker...)... I CAN login as regular user, I CAN sudo chmod 666 /dev/null... But it does not persist next time I reboot..

PS: we are talking about VPS, so root login is not allowed (in sshd)

Last edited by p4l4cl][n (2012-06-06 14:10:02)

brebs · 2012-06-06 14:49:15

It should be set in a udev rule:

$ grep null /lib/udev/rules.d/*
/lib/udev/rules.d/50-udev-default.rules:KERNEL=="null|zero|full|random|urandom", MODE="0666"

Your rules.d dir is probably different (different distro).

p4l4cl][n · 2012-06-06 14:55:14

brebs: thanks a lot /etc/udev/rules.d/ was empty, after I created file according to your post and rebooted, averythings seems ok now Thanks a lot again

falconindy · 2012-06-06 17:34:14

This isn't really a fix... /dev is devtmpfs these days which means its mostly kernel managed. /dev/null is created as mode 0666, and shouldn't be touched by udev. It would be better to find out what's causing the permissions to change than to blindly override it.

p4l4cl][n · 2012-06-06 17:43:11

I agree... but that's beyond my capabilities

Mister_Magotchi · 2012-06-08 22:57:26

I'm having the same issue as the OP, but as falconindy said, the fix used isn't really proper.

I'm using a VPS (OpenVZ), and the same happened to me after updating today (many parts of /dev lost the proper permissions, including null, zero, full, random, and urandom). I also don't have any files in /etc/udev/rules.d (although /usr/lib/udev/rules.d has a bunch of stuff).

Could someone please help point me in the right direction on finding the culprit for the change in permissions?

Also, the problem exists on two different VPS, but on a physical server I also run, the permissions are correct.

Last edited by Mister_Magotchi (2012-06-08 22:59:44)

p4l4cl][n · 2012-06-08 23:01:18

I am on openvz too...

Lucky · 2012-06-29 09:36:17

I talkt with falconindy, because i got the same problem so there is the fix (workaround). I know falconindy don't like override permission by udev, but maybe OpenVZ Container need this. If i had time, maybe i will look deeper in it.

Problem was upgrade from udev v182-4 to systemd-tools v184-2, because of removing the following line.

cat /etc/udev/rules.d/50-fix-permission.rules

# Thomas Lucke (Lucky) archlinux@builds.lucky.li
#
# In a OpenVZ container with enabled udev (systemd-tools), you run in some
# permission problems, because the udev rule was removed by this commit:
# http://cgit.freedesktop.org/systemd/systemd/commit/rules/50-udev-default.rules?id=378f2e074e38490103f999173bf717a5394170f8

# mem
SUBSYSTEM=="mem", KERNEL=="null|zero|full|random|urandom", MODE="0666"

btw. please post there if you get problems, because i don't follow the forum.
https://aur.archlinux.org/packages.php?ID=57949

rwd · 2012-07-03 05:41:00

Last edited by rwd (2012-07-03 05:41:41)

eEQK · 2020-11-04 08:36:14

I had the same problem that is issues with permissions of /dev/null
additionally, after I've fixed them, no terminal would start in X session
it was because I've created myself a new rule that was supposed to fix my adb permissions:

/etc/udev/rules.d/99-adb.rules

ATTRS{idVendor}=="2717", ATTRS{idProduct}=="4e42", ENV{ID_GPHOTO2}="1",
  ENV{GPHOTO2_DRIVER}="proprietary", ENV{ID_MEDIA_PLAYER}="1",
  MODE="0664", GROUP="plugdev"

now that I've removed this rule, everything (except for adb xD) works fine

V1del · 2020-11-04 08:51:32

You cannot and should not split udev rules on new lines, every new line is considered a new rule

Closing this 8 year old thread.

Arch Linux

#1 2012-06-06 13:54:01

[SOLVED]-bash: /dev/null: Permission denied

#2 2012-06-06 14:07:05

Re: [SOLVED]-bash: /dev/null: Permission denied

#3 2012-06-06 14:09:18

Re: [SOLVED]-bash: /dev/null: Permission denied

#4 2012-06-06 14:49:15

Re: [SOLVED]-bash: /dev/null: Permission denied

#5 2012-06-06 14:55:14

Re: [SOLVED]-bash: /dev/null: Permission denied

#6 2012-06-06 17:34:14

Re: [SOLVED]-bash: /dev/null: Permission denied

#7 2012-06-06 17:43:11

Re: [SOLVED]-bash: /dev/null: Permission denied

#8 2012-06-08 22:57:26

Re: [SOLVED]-bash: /dev/null: Permission denied

#9 2012-06-08 23:01:18

Re: [SOLVED]-bash: /dev/null: Permission denied

#10 2012-06-29 09:36:17

Re: [SOLVED]-bash: /dev/null: Permission denied

#11 2012-07-03 05:41:00

Re: [SOLVED]-bash: /dev/null: Permission denied

#12 2020-11-04 08:36:14

Re: [SOLVED]-bash: /dev/null: Permission denied

#13 2020-11-04 08:51:32

Re: [SOLVED]-bash: /dev/null: Permission denied

Board footer