Re: [suse-multimedia-e] Struggling with Audio CD access rights in SuSE 8.2
I always forget the default reply is to the original sender only, sorry for the double Jan ^^;
What puzzles me even more is that I have to give both commands everytime again after having booted. Shouldn't the chmod remain effective, also after boot ?
That's right, assuming nothing changes them. In a standard 8.2 installation if you look in /etc/pam.d files for xmd and gdm, you'll see they call a pam module called devperm. This module reads a /etc/logindevperm file, that states wich device should have their permissions changed and to what. Moreover, they change the owner of some devices to the logged in user. This is what's changing the devices permissions. What I dom't understand is why this isn't right for you: after all it should give you ownerships of the listed device, so your user should be able to use them. I have problem with this only when/if I log in with a different user in a different X session, but otherwise I'm fine. Oh, since I'me re-sendding this, I can as well add a maybe obvious tip: if you want to give permission for the devices to some groups, you can change the ownership of i.e. /dev/video0 to root:video this way the logging-in user is assigned ownership of the device, but the other users in the video group can still use the device. Then you go editing /etc/logindevperm to change the rights for the video devices from 0600 to 0660 :-) Ciao, Roberto.
On Monday 14 July 2003 12:13, r.maurizzi@digitalpha.it wrote:
I always forget the default reply is to the original sender only, sorry for the double Jan ^^;
What puzzles me even more is that I have to give both commands everytime again after having booted. Shouldn't the chmod remain effective, also after boot ?
That's right, assuming nothing changes them.
In a standard 8.2 installation if you look in /etc/pam.d files for xmd and gdm, you'll see they call a pam module called devperm. This module reads a /etc/logindevperm file, that states wich device should have their permissions changed and to what. Moreover, they change the owner of some devices to the logged in user. This is what's changing the devices permissions. What I dom't understand is why this isn't right for you: after all it should give you ownerships of the listed device, so your user should be able to use them. I have problem with this only when/if I log in with a different user in a different X session, but otherwise I'm fine.
Oh, since I'me re-sendding this, I can as well add a maybe obvious tip: if you want to give permission for the devices to some groups, you can change the ownership of i.e. /dev/video0 to root:video this way the logging-in user is assigned ownership of the device, but the other users in the video group can still use the device. Then you go editing /etc/logindevperm to change the rights for the video devices from 0600 to 0660 :-)
Ciao, Roberto.
Whoa, that's exactly what I am doing : logging in as 'root' and after that logging in as 'user' in a different X session ! Are your tips still valid then ? This requires some studying for me, since I'm relatively new in the Linux environment. In the meantime I have - temporarily - circumvented the problem by writing a small script containing both commands : chmod a+r /dev/cdrom chmod a=+rw /dev/mixer Now I run this script as 'root' first thing after booting and then all is fine (of course). Would there be any other approach in this multi X-session situation ? Greetings, -- Jan Elders Nuenen the Netherlands
On Tuesday 15 July 2003 21:18, Jan Elders wrote:
On Monday 14 July 2003 12:13, r.maurizzi@digitalpha.it wrote:
I always forget the default reply is to the original sender only, sorry for the double Jan ^^;
What puzzles me even more is that I have to give both commands everytime again after having booted. Shouldn't the chmod remain effective, also after boot ?
That's right, assuming nothing changes them.
In a standard 8.2 installation if you look in /etc/pam.d files for xmd and gdm, you'll see they call a pam module called devperm. This module reads a /etc/logindevperm file, that states wich device should have their permissions changed and to what. Moreover, they change the owner of some devices to the logged in user. This is what's changing the devices permissions. What I dom't understand is why this isn't right for you: after all it should give you ownerships of the listed device, so your user should be able to use them. I have problem with this only when/if I log in with a different user in a different X session, but otherwise I'm fine.
Oh, since I'me re-sendding this, I can as well add a maybe obvious tip: if you want to give permission for the devices to some groups, you can change the ownership of i.e. /dev/video0 to root:video this way the logging-in user is assigned ownership of the device, but the other users in the video group can still use the device. Then you go editing /etc/logindevperm to change the rights for the video devices from 0600 to 0660 :-)
Ciao, Roberto.
Whoa, that's exactly what I am doing : logging in as 'root' and after that logging in as 'user' in a different X session ! Are your tips still valid then ? This requires some studying for me, since I'm relatively new in the Linux environment. In the meantime I have - temporarily - circumvented the problem by writing a small script containing both commands : chmod a+r /dev/cdrom chmod a=+rw /dev/mixer Now I run this script as 'root' first thing after booting and then all is fine (of course).
Would there be any other approach in this multi X-session situation ? Greetings, -- Jan Elders
YES ! I just found the answer myself (by accident). The problem is indeed caused by running multiple X-sessions. If you want to run multisessions then : FIRST start your user session(s) -> no problem with accessing the Audio CD, THEN start your root session. No script is necessary ! Until now I did it in the reverse order (first 'root' then 'user') and then the 'user' will have no access permission to the CDROM. Ciao, -- Jan Elders Nuenen the Netherlands
participants (2)
-
Jan Elders -
r.maurizzi＠digitalpha.it