Joris Huizer wrote:
Greg wrote:which device do you write to ? (there's a reason I ask, I'll elucidate when sober...^hic)};)I call cdrecord as follows: cdrecord --force dev=ATA:1,0,0 that means, the ATA:1,0,0 devicehmm, as I think of that, I guess that's a scsi naming scheme; I think I read writing to /dev/cdrom would work to but I guess I never changed my cdrom-writing script to do so
At last!Not only am I not inebriated, but I remembered where I read what I based my missive on. :-)
http://cdrecord.berlios.de/old/private/man/README/README.ATAPI An extract from which goes as follows: "The ATAPI standard describes method of sending SCSI commands over IDE transport with some small limitations to the "real" SCSI standard. SCSI commands are send via IDE transport using the 'ATA packet' command. There is no SCSI emulation - ATAPI drives include native SCSI command support. For this reason, sending SCSI commands to ATAPI drives is the native method of supporting ATAPI devices. Just imagine that IDE is one of many SCSI low level transport mechanisms. This is a list of some known SCSI transports: - Good old Parallel SCSI 50/68 pin (what most people call SCSI) - SCSI over fiber optics (e.g. FACL - there are others too) - SCSI over a copper variant of FCAL (used in modern servers) - SCSI over IEEE 1394 (Fire Wire) - SCSI over USB - SCSI over IDE (ATAPI) As you now see, the use of the naming convention "ATAPI-SCSI emulation" is a little bit misleading. It should rather be called: "IDE-SCSI host adapter emulation" " Sooo, hopefully I was "wrong", but I knew what I really meant(?). HTH -- Ciao 4 now, Greg. # | mailto:unix@spiceisle.com # # --o-o-0-o-o-- Linux and Internet since 1992 # # To Live, To Love, To Learn, To Leave A Legacy. #