-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I try to use KsCD I get the following CD-ROM read or access error (or no audio disk in device) Please make sure you have access permissions to /dev/sr0, how do I correct this, this is from ls-l /dev/sr0> dbtrol@linux:~> ls -l /dev/sr0
brw------- 1 root root 11, 0 2002-04-12 10:42 /dev/sr0 dbtrol@linux:~> TIA David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+lNQ13VVncqMjOZsRAh0RAJ4xC/9VJU90NF8xkW7zM5jtv6g9AACgh9Aw 235P4fhrDHrxuahxdAl0Qik= =TgsM -----END PGP SIGNATURE-----
On Wednesday 09 April 2003 10:17 pm, DB Troll wrote:
When I try to use KsCD I get the following CD-ROM read or access error (or no audio disk in device) Please make sure you have access permissions to /dev/sr0, how do I correct this, this is from ls-l /dev/sr0> dbtrol@linux:~> ls -l /dev/sr0
brw------- 1 root root 11, 0 2002-04-12 10:42 /dev/sr0 dbtrol@linux:~>
TIA David ====================
David, sr0 doesn't really have much to do with the audio cds. Check your /dev/sg0 and/or /dev/sg1 permissions. They should probably be part of the audio group or cdrecording group, but owned by root. If that is the case, then you need to make you/user part of that group as well using YaST2. I think you will find the audio cds work ok then. Patrick -- --- KMail v1.5.9.1i --- SuSE Linux Pro v8.1 --- Registered Linux User #225206 On any other day, that might seem strange...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 O'Smith wrote:
Patrick, Checked the permissions of sg0,sg1 and kscd> dbtrol@linux:~> ls -l /dev/sg0 crw-r----- 1 root disk 21, 0 2002-04-12 10:42 /dev/sg0 dbtrol@linux:~> ls -l /dev/sg1 crw-r----- 1 root disk 21, 1 2002-04-12 10:42 /dev/sg1 dbtrol@linux:~> ls -l /opt/kde/bin/kscd ls: /opt/kde/bin/kscd: No such file or directory dbtrol@linux:~> ls -l /opt/kde3/bin/kscd -rwxr-xr-x 1 root disk 260820 2003-01-24 10:38 /opt/kde3/bin/kscd dbtrol@linux:~> They are all disk which I have made my self a part of that group with with YaST2 and it states configured and usable. Yet when I try to open it I get the same message. However if I use Konq as super user and go to /opt/kde3/bin/kscd it works fine. What am I missing in my setup. TIA David
====================
David, sr0 doesn't really have much to do with the audio cds. Check your /dev/sg0 and/or /dev/sg1 permissions. They should probably be part of the audio group or cdrecording group, but owned by root. If that is the case, then you need to make you/user part of that group as well using YaST2. I think you will find the audio cds work ok then.
Patrick
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+lP+S3VVncqMjOZsRAuc8AJ4znVLMo5MvBcGq9N1trYwLzgAIOACeN14V WoZQ+7Sv8OgblhAlf6tRNvY= =4N/S -----END PGP SIGNATURE-----
Am Donnerstag, 10. April 2003 07:22 schrieb DB Troll:
crw-r----- 1 root disk 21, 0 2002-04-12 10:42 /dev/sg0 dbtrol@linux:~> ls -l /dev/sg1 crw-r----- 1 root disk 21, 1 2002-04-12 10:42 /dev/sg1 dbtrol@linux:~> ls -l /opt/kde/bin/kscd ls: /opt/kde/bin/kscd: No such file or directory dbtrol@linux:~> ls -l /opt/kde3/bin/kscd -rwxr-xr-x 1 root disk 260820 2003-01-24 10:38 /opt/kde3/bin/kscd dbtrol@linux:~>
as super user and go to /opt/kde3/bin/kscd it works fine. What am I missing in my setup.
Well try to add 'w' for the group: chmod 660 /dev/sg0 ! Chris -- Christoph Dohmen ChDohmen@gmx.de
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christoph Dohmen wrote:
Am Donnerstag, 10. April 2003 07:22 schrieb DB Troll:
crw-r----- 1 root disk 21, 0 2002-04-12 10:42 /dev/sg0 dbtrol@linux:~> ls -l /dev/sg1 crw-r----- 1 root disk 21, 1 2002-04-12 10:42 /dev/sg1 dbtrol@linux:~> ls -l /opt/kde/bin/kscd ls: /opt/kde/bin/kscd: No such file or directory dbtrol@linux:~> ls -l /opt/kde3/bin/kscd -rwxr-xr-x 1 root disk 260820 2003-01-24 10:38 /opt/kde3/bin/kscd dbtrol@linux:~>
as super user and go to /opt/kde3/bin/kscd it works fine. What am I missing in my setup.
Well try to add 'w' for the group: chmod 660 /dev/sg0 !
Chris Thanks Chris, But that did not work. David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+lQtm3VVncqMjOZsRAiJOAKCFY/mu77iLSPytcubaXYpqM83HGgCZAY+1 Rg3p222z69wIZj5zIOVQngY= =HqKs -----END PGP SIGNATURE-----
Am Donnerstag, 10. April 2003 08:12 schrieb DB Troll:
Well try to add 'w' for the group: chmod 660 /dev/sg0 !
Thanks Chris, But that did not work.
Will don't know exactely. Is it the device no 0 or no 1 which you try to access??? So if it is device no 1 try chmod 660 /dev/sg1 ! Or try the same with devices sr? Chris -- Christoph Dohmen ChDohmen@gmx.de
On Thursday 10 April 2003 01:22 am, DB Troll wrote:
O'Smith wrote:
Patrick,
Checked the permissions of sg0,sg1 and kscd> dbtrol@linux:~> ls -l /dev/sg0
crw-r----- 1 root disk 21, 0 2002-04-12 10:42 /dev/sg0 dbtrol@linux:~> ls -l /dev/sg1 crw-r----- 1 root disk 21, 1 2002-04-12 10:42 /dev/sg1 dbtrol@linux:~> ls -l /opt/kde/bin/kscd ls: /opt/kde/bin/kscd: No such file or directory dbtrol@linux:~> ls -l /opt/kde3/bin/kscd -rwxr-xr-x 1 root disk 260820 2003-01-24 10:38 /opt/kde3/bin/kscd dbtrol@linux:~>
They are all disk which I have made my self a part of that group with with YaST2 and it states configured and usable. Yet when I try to open it I get the same message. However if I use Konq as super user and go to /opt/kde3/bin/kscd it works fine. What am I missing in my setup. TIA David
==================== David, You do not want to make the user part of the "disk" group, unless of course you want to take the chance of killing your hard drive setup and other nasty things! Plus if someone wanted to attack your user with a virus or something, they would have access to the "disk" group also! Not a good idea and not recommended. Do you have rw permissions for both owner and group on /dev/sg0?
What are you /dev/cdrom or /dev/cdrecorder linked too? My KSCD settings for cdrom is /dev/cdrom which is linked to /dev/sr0. ~> ls -l /dev/sg0 crw-rw---- 1 root cdrecording 21, 0 2002-09-09 16:24 /dev/sg0 cdrecording group was created by k3b, so if you are not using that program, you may not even have a cdrecording group. Use "audio" group then for it. Patrick -- --- KMail v1.5.9.1i --- SuSE Linux Pro v8.1 --- Registered Linux User #225206 On any other day, that might seem strange...
Am Donnerstag, 10. April 2003 15:32 schrieb O'Smith:
David, You do not want to make the user part of the "disk" group, unless of course you want to take the chance of killing your hard drive setup and other nasty things! Plus if someone wanted to attack your user with a virus or something, they would have access to the "disk" group also! Not a good idea and not recommended. Do you have rw permissions for both owner and group on /dev/sg0?
What are you /dev/cdrom or /dev/cdrecorder linked too? My KSCD settings for cdrom is /dev/cdrom which is linked to /dev/sr0. ~> ls -l /dev/sg0 crw-rw---- 1 root cdrecording 21, 0 2002-09-09 16:24 /dev/sg0
cdrecording group was created by k3b, so if you are not using that program, you may not even have a cdrecording group. Use "audio" group then for it.
I don't think that changing _ANY_ ownership in /dev tree is wanted by SuSE. If you don't want to mess with the SuSE scripting system, youu should check /etc/logindevperm. In this file there is a list of all devices, whose ownership should be automatically changed to the current user when logging in. If this doesn't work anymore, then you have messed with your system's pam configuration seriously. The file /etc/pam.d/xdm should contain the line: session required pam_devperm.so Check this and then use logindevperm file and if needed, add lines like: :0 0600 /dev/sg0:/dev/sg1:/dev/sg2:/dev/sg3 :0 0600 /dev/sr0:/dev/sr1:/dev/sr2:/dev/sr3 Greets, Daniel
On Thursday 10 April 2003 20:42, Daniel Eckl wrote:
Am Donnerstag, 10. April 2003 15:32 schrieb O'Smith:
David, You do not want to make the user part of the "disk" group, unless of course you want to take the chance of killing your hard drive setup and other nasty things! Plus if someone wanted to attack your user with a virus or something, they would have access to the "disk" group also! Not a good idea and not recommended. Do you have rw permissions for both owner and group on /dev/sg0?
What are you /dev/cdrom or /dev/cdrecorder linked too? My KSCD settings for cdrom is /dev/cdrom which is linked to /dev/sr0. ~> ls -l /dev/sg0 crw-rw---- 1 root cdrecording 21, 0 2002-09-09 16:24 /dev/sg0
cdrecording group was created by k3b, so if you are not using that program, you may not even have a cdrecording group. Use "audio" group then for it.
I don't think that changing _ANY_ ownership in /dev tree is wanted by SuSE.
If you don't want to mess with the SuSE scripting system, youu should check /etc/logindevperm.
In this file there is a list of all devices, whose ownership should be automatically changed to the current user when logging in.
If this doesn't work anymore, then you have messed with your system's pam configuration seriously.
The file /etc/pam.d/xdm should contain the line: session required pam_devperm.so
Check this and then use logindevperm file and if needed, add lines like: :0 0600 /dev/sg0:/dev/sg1:/dev/sg2:/dev/sg3 :0 0600 /dev/sr0:/dev/sr1:/dev/sr2:/dev/sr3
Greets, Daniel
Oh yes, this confusing ownership system of SuSE. I find it very irritating. it causes most of the cdrecording apps to have problems, which are leading to a lot of frustration, and many posts here. Example: Most cdrecording apps try to read the cd reader / writer as root, however the app then is started as the user, so if the rights are set to user only, then the app, when trying to do something as root on this device, fails! K3b setup installs its group cdrecording and tries to set the rights correctly, and it seems to work, but latest next time you login k3b does not find any devices anymore, because root cannot read them anymore, only the user has rw access. Now add to that that the cdwriter / cdrom is sometimes referred to as /dec/sr0 and sometimes as sg0, and the confusion is perfect. Some apps seem to be even hardwired to one or the other. I prefer a group, such as disk or cdrecording, scanner, audio, disk, to contain the users having the rights to access a device or a group of devices. This is much more easy for my tired brain to understand. So I switch off logindevperm, and set up my groups as I can understand it, and now no more surprises, it works and keeps working. (BTW, thanks to Anders for explaining the logindevperm stuff to me some time ago, since then I always get my cdwriter to work!) It does not matter to a virus, if I have the right to access a disk device from logindevperm or from being member of a group, doesn't it??? I'm not aware of a way to avoid giving a user rw access to a hdd and still being able to use this hdd, so whatever I do, if I get a virus it has my rights, which usualy include disk access. Please correct me if got it wrong! Regards, Matt T. PS. Don't get me wrong, I think SuSE Linux is a great distribution, this is just an areas where I see improvements are possible and necessary.
Am Freitag, 11. April 2003 15:00 schrieb Matt T.:
Most cdrecording apps try to read the cd reader / writer as root, however the app then is started as the user, so if the rights are set to user only, then the app, when trying to do something as root on this device, fails! K3b setup installs its group cdrecording and tries to set the rights correctly, and it seems to work, but latest next time you login k3b does not find any devices anymore, because root cannot read them anymore, only the user has rw access.
Now add to that that the cdwriter / cdrom is sometimes referred to as /dec/sr0 and sometimes as sg0, and the confusion is perfect. Some apps seem to be even hardwired to one or the other.
I prefer a group, such as disk or cdrecording, scanner, audio, disk, to contain the users having the rights to access a device or a group of devices. This is much more easy for my tired brain to understand. So I switch off logindevperm, and set up my groups as I can understand it, and now no more surprises, it works and keeps working.
(BTW, thanks to Anders for explaining the logindevperm stuff to me some time ago, since then I always get my cdwriter to work!)
It does not matter to a virus, if I have the right to access a disk device from logindevperm or from being member of a group, doesn't it???
I'm not aware of a way to avoid giving a user rw access to a hdd and still being able to use this hdd, so whatever I do, if I get a virus it has my rights, which usualy include disk access.
Please correct me if got it wrong!
Regards, Matt T. PS. Don't get me wrong, I think SuSE Linux is a great distribution, this is just an areas where I see improvements are possible and necessary.
Sorry for the wrong mail some minutes ago..... Am Freitag, 11. April 2003 15:00 schrieb Matt T.:
Example: Most cdrecording apps try to read the cd reader / writer as root, however the app then is started as the user, so if the rights are set to user only, then the app, when trying to do something as root on this device, fails! K3b setup installs its group cdrecording and tries to set the rights correctly, and it seems to work, but latest next time you login k3b does not find any devices anymore, because root cannot read them anymore, only the user has rw access.
Are you sure? root should be able to do anything, no matter what rights are specified.
Now add to that that the cdwriter / cdrom is sometimes referred to as /dec/sr0 and sometimes as sg0, and the confusion is perfect. Some apps seem to be even hardwired to one or the other.
Yes, you have to fix rights on both, just to be sure.
I prefer a group, such as disk or cdrecording, scanner, audio, disk, to contain the users having the rights to access a device or a group of devices. This is much more easy for my tired brain to understand. So I switch off logindevperm, and set up my groups as I can understand it, and now no more surprises, it works and keeps working.
Yes, that's my way to do that, too. But if s.o. wants to be sure, that all SuSE scripts are doing what they are supposed to, you should not mess with that. Only if you know how something works, you can tweak it this way.
It does not matter to a virus, if I have the right to access a disk device from logindevperm or from being member of a group, doesn't it???
Sure there's a difference. logindevperm does _not_ set the owner /dev/hd* or /dev/sd* to the user. Just the cdrom devices. So a virus could erase the CD-RW in your CD writer, but cannot do something with your harddisks.
I'm not aware of a way to avoid giving a user rw access to a hdd and still being able to use this hdd, so whatever I do, if I get a virus it has my rights, which usualy include disk access.
There's a difference between let a user write files and let a user have write access to the physical hdd device entry... In the second case, the user can overwrite the mba, or do anyting he wants to.
Please correct me if got it wrong!
Sure I will :))))
PS. Don't get me wrong, I think SuSE Linux is a great distribution, this is just an areas where I see improvements are possible and necessary.
I know what you mean. I think the default setting is wonderful for users, but bad for admins and experienced users. But the latter one can change this easily. Greets, Daniel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 O'Smith wrote:
On Thursday 10 April 2003 01:22 am, DB Troll wrote:
O'Smith wrote:
Patrick,
Checked the permissions of sg0,sg1 and kscd> dbtrol@linux:~> ls -l /dev/sg0
crw-r----- 1 root disk 21, 0 2002-04-12 10:42 /dev/sg0 dbtrol@linux:~> ls -l /dev/sg1 crw-r----- 1 root disk 21, 1 2002-04-12 10:42 /dev/sg1 dbtrol@linux:~> ls -l /opt/kde/bin/kscd ls: /opt/kde/bin/kscd: No such file or directory dbtrol@linux:~> ls -l /opt/kde3/bin/kscd -rwxr-xr-x 1 root disk 260820 2003-01-24 10:38 /opt/kde3/bin/kscd dbtrol@linux:~>
They are all disk which I have made my self a part of that group with with YaST2 and it states configured and usable. Yet when I try to open it I get the same message. However if I use Konq as super user and go to /opt/kde3/bin/kscd it works fine. What am I missing in my setup. TIA David
====================
David, You do not want to make the user part of the "disk" group, unless of course you want to take the chance of killing your hard drive setup and other nasty things! Plus if someone wanted to attack your user with a virus or something, they would have access to the "disk" group also! Not a good idea and not recommended. Do you have rw permissions for both owner and group on /dev/sg0?
What are you /dev/cdrom or /dev/cdrecorder linked too? My KSCD settings for cdrom is /dev/cdrom which is linked to /dev/sr0. ~> ls -l /dev/sg0 crw-rw---- 1 root cdrecording 21, 0 2002-09-09 16:24 /dev/sg0
cdrecording group was created by k3b, so if you are not using that program, you may not even have a cdrecording group. Use "audio" group then for it.
Patrick Thanks Patrick, I have now removed disk from my user. My KSCD setting for cdrom is /dev/sr0. Ls -l > crw-rw---- 1 root disk 21, 0 2002-04-12 10:42 /dev/sg0 dbtrol@linux:~> I am not sure of how to check for links though. David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+lXfT3VVncqMjOZsRAnZ1AJ9qEC3k+QQsZSk5mjrcEMVcdy31ZACghCqV xg/cBV7Guv0nsYcBEjOsZu8= =11uW -----END PGP SIGNATURE-----
On Thursday 10 April 2003 09:55 am, DB Troll wrote:
====================
David, You do not want to make the user part of the "disk" group, unless of course you want to take the chance of killing your hard drive setup and other nasty things! Plus if someone wanted to attack your user with a virus or something, they would have access to the "disk" group also! Not a good idea and not recommended. Do you have rw permissions for both owner and group on /dev/sg0?
What are you /dev/cdrom or /dev/cdrecorder linked too? My KSCD settings for cdrom is /dev/cdrom which is linked to /dev/sr0. ~> ls -l /dev/sg0 crw-rw---- 1 root cdrecording 21, 0 2002-09-09 16:24 /dev/sg0
cdrecording group was created by k3b, so if you are not using that program, you may not even have a cdrecording group. Use "audio" group then for it.
Patrick
Thanks Patrick, I have now removed disk from my user. My KSCD setting for cdrom is /dev/sr0. Ls -l > crw-rw---- 1 root disk 21, 0 2002-04-12 10:42 /dev/sg0
dbtrol@linux:~>
I am not sure of how to check for links though. David =======================
You can do that the same way, ls -l /dev/cdrom. Mine shows: lrwxrwxrwx 1 root root 8 2002-12-06 19:44 /dev/cdrom -> /dev/sr0 Notice the arrow pointing to the /dev/sr0? That's telling you what /dev/cdrom is linked too. Ok, I think all you need do now is make /dev/sg0 & /dev/sg1 part of the audio group and make sure you are in the audio group as well as user. If you only have one drive you can do just the one, but I do both sg0 & sg1 the same, so I can use either drive for audio cds. To change the groups using the gui rather than in a shell, I just start up a Konq session as root. You should have a selection for File Manager - Super User in your menu or you can open a shell and type "kdesu konqueror" to start it as root. Go to /dev/, find your sg0 & sg1 icons, right click, select Properties>Permissions tab and change the group from disk to audio! Patrick -- --- KMail v1.5.9.1i --- SuSE Linux Pro v8.1 --- Registered Linux User #225206 On any other day, that might seem strange...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 O'Smith wrote:
On Thursday 10 April 2003 09:55 am, DB Troll wrote:
====================
David, You do not want to make the user part of the "disk" group, unless of course you want to take the chance of killing your hard drive setup and other nasty things! Plus if someone wanted to attack your user with a virus or something, they would have access to the "disk" group also! Not a good idea and not recommended. Do you have rw permissions for both owner and group on /dev/sg0?
What are you /dev/cdrom or /dev/cdrecorder linked too? My KSCD settings for cdrom is /dev/cdrom which is linked to /dev/sr0. ~> ls -l /dev/sg0 crw-rw---- 1 root cdrecording 21, 0 2002-09-09 16:24 /dev/sg0
cdrecording group was created by k3b, so if you are not using that program, you may not even have a cdrecording group. Use "audio" group then for it.
Patrick
Thanks Patrick, I have now removed disk from my user. My KSCD setting for cdrom is /dev/sr0. Ls -l > crw-rw---- 1 root disk 21, 0 2002-04-12 10:42 /dev/sg0
dbtrol@linux:~>
I am not sure of how to check for links though. David
=======================
You can do that the same way, ls -l /dev/cdrom. Mine shows:
lrwxrwxrwx 1 root root 8 2002-12-06 19:44 /dev/cdrom -> /dev/sr0
Notice the arrow pointing to the /dev/sr0? That's telling you what /dev/cdrom is linked too. Ok, I think all you need do now is make /dev/sg0 & /dev/sg1 part of the audio group and make sure you are in the audio group as well as user. If you only have one drive you can do just the one, but I do both sg0 & sg1 the same, so I can use either drive for audio cds. To change the groups using the gui rather than in a shell, I just start up a Konq session as root. You should have a selection for File Manager - Super User in your menu or you can open a shell and type "kdesu konqueror" to start it as root. Go to /dev/, find your sg0 & sg1 icons, right click, select Properties>Permissions tab and change the group from disk to audio!
Patrick
Hello Patrick,
lrwxrwxrwx 1 root root 9 2003-04-08 19:31 /dev/cdrom -> /dev/scd0 dbtrol@linux:~> ls -l /dev/scd0 brw------- 1 dbtrol users 11, 0 2002-04-12 10:42 /dev/scd0 dbtrol@linux:~>
I am really confused now. David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+lZUO3VVncqMjOZsRAq3zAJ90Ec549lE9vxpPpvIkwsOfh/+g8gCfQA/4 UPPi29Stznusuk2GS3PFd2s= =thFE -----END PGP SIGNATURE-----
On Thursday 10 April 2003 09:17, DB Troll wrote:
When I try to use KsCD I get the following CD-ROM read or access error (or no audio disk in device) Please make sure you have access permissions to /dev/sr0, how do I correct this, this is from ls-l /dev/sr0> dbtrol@linux:~> ls -l /dev/sr0
brw------- 1 root root 11, 0 2002-04-12 10:42 /dev/sr0 dbtrol@linux:~>
TIA David
if KsCD complains about /dev/sr0, it probably tries to read this device, and this is accessible for root only in your setup. 1) Change permissions of /dev/sr0 to be in group "disk" and readable there, as you have done for /dev/sg0 2) Check the archives of this list here, you probably need to adjust some links for sg0 sr0 etc, and that had been discused here already. HTH, Matt T.
participants (5)
-
Christoph Dohmen
-
Daniel Eckl
-
DB Troll
-
Matt T.
-
O'Smith