Michal Hlavac wrote:
There is no burn group in SUSE, at least not in 10.0.
Access rights are given during console login by setting file ACLs.
This is done by resmgr, see /usr/share/doc/packages/resmgr/.
Do a getfacl /dev/sr0 (or whatever your CD-Writer-Device is) to see
the ACLs.
The only remaining question is if there shouldn't be write access to
the corresponding generic SCSI device as well, or if that isn't needed.
when I start k3b (suse 10.2) it says this:
cdrecord will be run without root privileges
It is highly recommended to configure cdrecord to run with root privileges.
Only then cdrecord runs with high priority which increases the overall
stability of the burning process. Apart from that it allows changing the size
of the used burning buffer. A lot of user problems could be solved this way.
This is also true when using SuSE's resmgr.
Solution: Use K3bSetup to solve this problem.
Interesting information.
k3bsetup sets cdrecord setuid-root, doesn't it? How do you prevent
that it is set back to 755, according to /etc/permissions, when
SuSEconfig is run the next time? (This is done by the module
/sbin/conf.d/SuSEconfig.permissions and controlled by
/etc/sysconfig/security.)
If cdrecord needs to run with root privileges, it should be
installed so from the start and not changed by k3bsetup, IMHO. The
latter won't survive for long in a standard SUSE setup, the setuid
bit will disappear after the next sysadmin activity that causes
SuSEconfig to run.
Joachim
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: [EMAIL PROTECTED]
Roedermark, Germany
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
