Re: cdrecord -scanbus giving strange results.
> What I did to fix k3b was to put dev=ATAPI:0,0,0 in as a user
> parameter for cdrecord, and run k3b via sudo. Looking at the log,
> for some reason k3b wants to use "dev=/dev/hdc" without any means
> to change it. Now, the log shows "dev=/dev/hdc dev=ATAPI:0,0,0"
> as the command line being used and cdrecord uses the latter in
> burning.
>
> Use sudo (set it up for "NOPASSWD: /usr/bin/k3b"), and remove
> any suid bits on the cdrecord binaries. I use kernel.org 2.6.11.10
> and all is well.
>
How do I "put dev=ATAPI:0,0,0 in as a user parameter for cdrecord" ??
I'm used to edit the file /dev/default/cdrecord...
Vegard
>
Reply to: