On Monday 24 December 2001 13.15, Rosanne DiMesio wrote:
Thought I'd post the answer, since the problem turned out to be the way Yast2 had set some things up, and mine was a default installation.
First, I had to add myself to the disk group - Yast2 hadn't done it.
Second, Yast2 had both /dev/cdrecorder and /dev/cdrom pointing to /dev/sr0. I don't know why, shouldn't /dev/cdrom have pointed to /dev/scd0, or am I misunderstanding things? In any case, the permissions for /dev/scd0 are what needed to be changed - once I gave the group (disk) write access for it, autodetect worked. It also works to simply enter /dev/scd0 as the audio io slave.
All this should be in the FAQ already. It is a very frequently asked question.
Now, a question. In the process of trying to fix this, I discovered that the owner and group for /dev/sr0 changes according to who I'm logged in as. If I log in as root, the owner and group are root. If l log in as myself, I am the owner and users is the group. Log in as another user, that user is the owner with users as group. This is not the case with any of my other drives, all of which are root owner and disk group regardless of who I log in as. Is this typical for Linux, or is it another Yast2 setup peculiarity? Any explanation as to why a cdwriter would be set up this way, and not any other drives?
A regular user should as a general rule not have device level access to hard disk partitions, as this would set aside all unix style permission settings. A cd writer otoh is another matter. Merry Christmas Anders