Specifications

specify the switch −data for cdrecord on the command line.
The images for the second and subsequent sessions are a little bit more complicated to generate. Mkisofs
must know where the free space on the CD−R begins. That information can be gathered by using the option
−msinfo on cdrecord (see example below).
shell> NEXT_TRACK=`cdrecord −msinfo dev=0,6,0`
shell> echo $NEXT_TRACK
shell> mkisofs −R −o cd_image2 −C $NEXT_TRACK −M /dev/scd5
private_collection/ \
For more information, please read the file README.multi, which is distributed with cdrecord.
4.19 Should I use the SCSI adapter shipped with the writer?
Reported via email: Most CD−writer docs say to use a separate SCSI bus if going from a CD−ROM to a
CD−writer and I have seen this myself in the following scenario:
Adaptec 2940UW SCSI card, a 24x SCSI CD−ROM and a 4x4 SCSI CD−writer. When I got the CD−writer,
it came with its own ISA SCSI card which could only handle one device. I figured I'd toss this and use my
better adaptec card for all the stuff. I noticed it was quite prone to buffer under−runs when recording at the 4x
speed, but as soon as I tried hooking up the ISA SCSI card, it had no problems. I know 2 other people (both
using adaptec 2940 cards), who have experienced exactely the same symptoms, usually when writing from a
CD−ROM to a CD−recorder. Though I've never experienced the problem when going from a hard drive to a
CD−writer on the same bus.
4.20 How to burn over the network?
Usally a file transfer with FTP is fast enough to feed a CD−recorder at quadruple (4x) speed even over a 10
Mbit ethernet. You can couple the ftp−client and cdrecord via a fifo. First create a fifo named cdimage:
mkfifo cdimage
ftp other.host.org
get cdimg cdimage
Then treat cdimage like a regular file, i.e. issue the following command:
cdrecord dev=0,1,0 speed=2 cdimage
CD−Writing HOWTO
4.19 Should I use the SCSI adapter shipped with the writer? 29