udev sets the permissions of /dev/cdrom and /dev/cdroms/cdrom0 to root:cdrom as usual but as they are symlinks to /dev/hdc on my ide machine... burrito% eject /dev/cdrom eject: unable to open `/dev/hdc' where /dev/hdc 's permissions are brw-rw---- 1 root root giving errors such as that above
There have been virious discucssions over this. See the linux-hotplug-devel list for details. It should work wiuth the latest udev, what version do you use? Can you please try the ~x86 version?
tried the latest udev version, 50, was using 45 ... same problem, only now /dev/cdrom and /dev/cdroms/cdrom0 have permissions root:root as well as /dev/hdc, though this makes little difference either way, being only symlinks ...
Can you please try to run udevstart? on my system its like this: # ls /dev/hdc -l brw-rw---- 1 root root 22, 0 Jan 28 12:44 /dev/hdc # udevstart # ls /dev/hdc -l brw-rw---- 1 root disk 22, 0 Jan 28 12:44 /dev/hdc
Ran udevstart and did an ls -la /dev/hdc and the permissions are fixed!! brw-rw---- 1 root cdrom 22, 0 Nov 18 08:35 /dev/hdc excellent, thanks :D But what exactly was happening?
I dont know why the permissions are root:root at the beginning and you need to run udevstart .. maybe someone else has overridden the permissions, maybe the cdrom detection did not work when the system was started? however, it sucks to have to run udevstart after every boot/reboot to get :cdrom as group
Oh, so I have to run udevstart after every boot? dang. I thought it was fixed for a second there. Is this behaviour common for udev? I mean, I could write a script to run udevstart for me, but that would just be a bandaid fix. Is there nothing I can set in /etc/udev to change this? Thanks
No, that means something like pam or something else is modifying your permissions of the device, and it's not a udev problem. Take a look and see if pam is doing this.
