Joerg Schilling wrote:
If you require write access then you can't read a CD, because you have to *write* the commands to the device. Therefore only a number of known commands are allowed with read-only access. A larger set is allowed if you have write access, but you must be root to send commands which are known dangerous (flash device BIOS for instance) or which do unknown actions, such as vendor specific commands.Bill Davidsen <davidsen@tmr.com> wrote: I do understand the basics, you are not willing to stop sending commands outside the normal mmc set, and while these commands may be safe by your standard, the kernel does not, and should not, have exceptions for every devices which burns optical media. The fact that other software works where your does not shows that the commands are not needed to write a CD (although I'm sure they're desirable for optimal performance). No FUD, other work, your doesn't, it's not your week to be God so you're wrong. My version has a cdrecord in /usr/bin which works. I didn't build it, therefore it's a Fedora-supplied version AFAIK. And it works as a normal user, so maybe you could get the source and find out how they fixed the bug.Cdrecord is far away from being irrelevent. On the other side, cdrskin is irrelevent as it is not portable. The broken debian fork is irrelevent as it is missing a lot of important features and as it does not work (as reported by people wo did find it on their distributuion). BTW: there is nothing like Fedora cdrecord. You are either uninformed or a bad guy who intentionally spready FUD. -- bill davidsen <davidsen@tmr.com> CTO TMR Associates, Inc Doing interesting things with small computers since 1979 |