Annoying cdrw permissions problem.
Annoying problem with my cdrw drive: I can never get it to keep its permissions. Everytime I put a cd in, I have at chmod a+r /dev/hdc. not sure why... This only started happening when I upgraded to kernel 2.6.10. I think it has something to do with udev, not sure...
I have this: Code:
# permissions for IDE CD devices |
Not playing with udev yet, but I'm fairly sure I remember reading that there is also another udev-specific file involved.
Also, your system-wide umask (man umask) may still have something to do with it. But from your 'code', it might be udev itself, so may I suggest you search here and at www.google.com/linux for any possible reports/fixes? Your search term should probably be in the advanced box as 'all words' needing udev and cd. hth, |
I haven't yet played with udev much but your problem has sparked in me an interest with it, so I'm looking into it.
Do you have any files in /etc/udev/permissions.d/ ? I am running Fedora Core 3 with kernel 2.6.9 & this is were the files that define the udev device permissions reside in FC3. If you are defining the perms in both /etc/udev/rules.d/udev.rules & /etc/udev/permissions.d/*.permissions then there might be a fight between these two as to what perms to use. If you do have any files in /etc/udev/permissions.d/, post their contents & we'll try to get to the bottom of this. Also, run: ls -R /etc/udev/ & post results. |
$ ls -R /etc/udev/
/etc/udev/: permissions.d/ rules.d/ scripts/ udev.conf /etc/udev/permissions.d: udev.permissions udev.permissions~ /etc/udev/rules.d: 10-local.rules compat.rules.unsupported udev.rules 10-local.rules~ devfs.rules.unsupported udev.rules~ /etc/udev/scripts: floppy-extra-devs.sh* ide-devfs.sh* make_extra_nodes.sh* scsi-devfs.sh* ...is what I got. Also, here's the contents of /etc/udev/permissions.d/udev.permissions : (I think you'll find the only interesting section is "Optical Devices") So, yeah it looks like I may be defining the permissions for the drive twice, but so? I define them the same way: 0666 Code:
|
I just remembered!!!
I had the same trouble when I first went to the 2.6 kernel. The way you are supposed to do this now is to add any user that wants cdrom access to the "disk" group. As root: usermod -G disk <user_name> You might also want to undo any changes you made to your udev files. |
hey fuzzyash: didn't work. oh and by the way, don't use KUser to change user/group permissions... it will only end in pain!
what changes in the udev files should I undo? I don't even remember the order I made them in :( |
Quote:
I use this configuration file with a couple of additions at the end: Code:
BUS="ide", ID="1.0", SYMLINK="cdrom" |
Lord Zoltar:
I was having a problem with my cdrom and dvd drives when I upgraded to the 2.6.11.9 kernel. I found the udev would change the links in /dev everytime I booted up. I had /dev set like this: Code:
cdrom -> hdc Code:
cdrom -> hdd |
Quote:
Problems arise with simply uninstalling udev. Lets face it, most average users out there running Linux at home are gonna want to add a hard drive, plug in a USB memory stick or mp3 player or something of that description at some stage. udev was specifically developed to help make adding devices to the system much simpler & faster, making Linux more user friendly for those who want to use a reliable OS, but don't want to become an absolute expert. All they want is for their computer to do what they want, without having to go through a steep learning curve to what most would consider an easy task, like simply downloading the pics off their digital camera for example. So the problem with uninstalling udev is that if you ever want to add or remove devices to or from your system, then you will need to go to a great deal more trouble to get them to work. This might be alright for those of us who enjoy learning all their is to know about every task that they preform, but for most users, this is a pain in the arse! Alright, back to the problem... A couple of posts ago I said: Quote:
Run: Code:
ls -l /dev/hdc Harmaa Kettu, you obviously know more about udev & how it works than I do. Could you please explain your answer, in other words, why this works? Could you also please post a link to where to find a good tutorial site on udev & how to configure it, if you know of one of course! Thanks! |
All times are GMT -5. The time now is 09:46 AM. |