Paul W. Abrahams wrote:
With the suid root, why would it also be necessary to change the group, I wonder?
Not sure, that is what xcdroast did to setup non-root burning, and since it worked...
And turning that around, if I'm in the cdburn group, why would the suid root be necessary?
Not sure, but both xcdroast and k3b-setup say to do this for non-root burning.
Given the hazards of getting clobbered by a kernel update, why not do root.root 755 in the first place?
That is the default and you said you were having trouble burning as non-root. You said this was on 9.1, and as I recall that is what I needed to do, and it worked when I had 9.1. There was a major change in the 2.6.8 kernel that changed the way many programs could access kernel privileged signals, which broke cdrecord in non-root mode, but which has been fixed in 9.2. This requires it to NOT be suid, the opposite of 9.1 with the default kernel. If you put the changes in /etc/permissions.local, they will always be respected and will last through a distro upgrade, not to mention a kernel update. But I was warning you that if the changes in the way the kernel treated cdrecord was backported, it would then be the CAUSE of non-root failing. Hope that helps to explain what I was saying. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871