Joerg Schilling wrote:
When are you going to fix that? Other software can burn without being root, clearly it can be done. If there are better commands to use with a drive a check can be made to see if cdrecord is running as root. Actually I thought that you had provided an option, -mmc or similar, to use only the commands common to the standard. As people become more careful about security fewer systems will allow setuid root programs.>From zoubidoo@hotmail.com Fri Jan 30 21:07:19 2009You did not install cdrecord correctly as you see from this messages. Cdrecord needs to be installed suid root in order to be able to open all needed devices and in order to send all needed SCSI commands.
Time to learn to use a scalpel instead of a chain saw... You don't just "kill hald" on most modern distributions, things stop working. And the problem is not in hald at all, it's in the rules given to hald for handling the drive, usually a 70_something rule, which you can edit or remove to prevent probing and automounting. This problem looks like firmware or bad media though.Trying to clear drive status.This may be from a drive firmware bug or frim running hald (hald is non-cooperatively).Try to kill hald and retry cdrecord after correctly installing it suid root.
-- E. Robert Bogusta It seemed like a good idea at the time