/dev/* permissions

This forum is for all other ARMv5 devices

/dev/* permissions

Postby ellis » Thu Jun 14, 2012 9:25 pm

After a recent reboot, I was getting errors from various applications on my Classic B01 that /dev/null: Permission denied. This would cause those applications to fail. Performing 'sudo chmod 666 /dev/null' corrected this, but the change is not persistent over a reboot. transmissiond also refused to start from rc.d, and this was solved by changing permissions to 666 on /dev/urandom (my /var/log/erros.log file was being spammed with thousands of errors about random number sourcing).

Has anyone else encountered such a problem? I can't be sure that this is a Pogoplug specific problem or as a result of a general blunder on my part. :)
ellis
 
Posts: 1
Joined: Thu Jun 14, 2012 9:22 pm

Re: /dev/* permissions

Postby Geoff » Mon Jun 18, 2012 8:44 pm

$this->bbcode_second_pass_quote('ellis', 'H')as anyone else encountered such a problem?

Yes, I got this after running the latest update-oxnas script to update the kernel. By comparing the nodes in the /dev tree pre- and post-update, I found a several that I guess need fixing, including the ones that you found. I kludged fixes to these by adding the following lines to /etc/rc.local:$this->bbcode_second_pass_code('', 'chmod go+rw /dev/{full,null,random,urandom,zero}
chmod o+t /dev/{fuse,net/tun}')
Geoff
 
Posts: 231
Joined: Wed Mar 09, 2011 5:14 pm

Re: /dev/* permissions

Postby portnumber53 » Mon Jun 25, 2012 8:02 am

This fixes the /dev/null permission denied problem more permanently

make sure you have something like
-----------------------------------
KERNEL=="null", MODE="0666"
--------------------
on /etc/udev/rules.d/40-basic-permission.rules
portnumber53
 
Posts: 2
Joined: Mon Jun 25, 2012 1:30 am

Re: /dev/* permissions

Postby karog » Wed Jun 27, 2012 3:16 pm

I ran into this /dev/{null,zero,full,random,urandom} permissions problem after rebuilding with the new kernel and latest rootfs.

WarheadsSE, would you please offer the proper solution for this?

In the mean time, I created /usr/lib/udev/rules.d/50-mode-dev-null-full-zero-random-urandom.rules containing the following lines:
$this->bbcode_second_pass_code('', '
# mem
SUBSYSTEM=="mem", KERNEL=="null|zero|full|random|urandom", MODE="0666"
')
I created a new file rather than modify 50-udev-default.rules since it gets overwritten on some pacman updates.

Reboot after this change.

I don't think this is the correct long term solution but it seems to do for now.
karog
 
Posts: 305
Joined: Thu Jan 05, 2012 7:55 pm


Return to Community Supported

Who is online

Users browsing this forum: No registered users and 46 guests