Paul Howarth wrote:
On Wed, 2005-03-09 at 16:07 +0900, Mark Sargent wrote:
Mark Sargent wrote:
Hi All,
sometimes I load a scsi cd-rw at boot. It's always loaded as /dev/hdc. I have a coupla Qs about permissions etc. When it's loaded each time, does the file /dev/hdc permissions get altered each time.? I ask this, because, 2 dys ago, I changed the permissions of the file to 666, so as to allow K3b to burn in root mode. This is because the burn process stops mid burn with a 254 error stating cdrecord is not being run with root priviliges. But, the permissions are back as 600 today. I would have thought the file's permissions stay changed despite the loading or not of a block device to that file.? Am I wrong..?
Hi All,
just to delve into this a little more; what are the default udev permissions/ownership for /dev/hdc /dev/scd0.? I get the following,
[root@localhost dev]# ls -alh hdc scd0 brw------- 1 coolboarderguy disk 22, 0 Mar 9 2005 hdc brw------- 1 coolboarderguy disk 11, 0 Mar 9 2005 scd0
Shouldn't they be owned by root..? If no, then I get problems with cdrecorder/K3b. Burning stops mid-burn and gives the 254 error saying that cdrecorder is not with root priviliges. Little confused. Cheers.
You'll find there's a symlink created by udev:
/dev/cdwriter -> hdc
The device pointed to by this symlink will be owned by the currently- logged-in user, so that they can access the device.
See /etc/security/console.perms
The idea is to support cd burning as a non-root user, but it appears that this isn't working...
Paul.
Hi All,
thanx, Paul. I can only get K3b to burn with /dev/scd0 at 666 permissions. Anything else and I get an error message, halfway through the burn process, along with permanently non-usable media(cd-r type). Cheers.
Mark Sargent.
