Recently I asked about using cdrecord on my NetBSD/macppc-current,
because it would not open the SCSI library.

Today I played with it again with the updated pkgsrc cdrecord-current.

After having added SCSIDEBUG to the kernel and tried to find out whether
the configuring of the cd record actually completed, I observed that
cdrecord caused activities on my CD-ROM (cd0 on atapibus) when I tried to address
the recorder (cd1 on scsi). I don't know why.

I also observed that cdrecord dev=/dev/rcd0c -prcap would actually print
the capabilities of the cdrom drive.

I then removed 'cd* on atapibus...' from the kernel, and voila, now
cdrecord can see and query the cd recorder (now on cd0). It is now
happily blanking a CD-RW.

I've not done any analysis of why cdrecord (or the kernel) talks to cd0 on
atapi when I ask it to work with cd1 on scsi, but I'll take a look at it
sometime, but I wanted to mention it to the public at large -- maybe
someone even knows what is going on :-)

- Erik Bertelsen