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.