[NTLUG:Discuss] Using 2 CD-ROM's with X-CD-Roast

Kevin Brannen kbrannen at gte.net
Mon Aug 16 11:36:13 CDT 1999


Seth Daniel wrote:
> 
> > I ditched X-CD-Roast in favor of cdrecord, and it works great now :)
> >
> > -Reeves
> 
> Isn't X-CD-Roast a frontend to cdrecord?  I ask because I'm
> going to be getting a cd burner and I'd like to have the
> appropriate tools setup when I do get it.
> --

Yes, but it's not like cdrecord is hard to use either.  I'll include my
"mkcd" script at the bottom of this message.  It's hardwired to my dir
layout, but I'll add a few comments to help you.

Once I got my files set up, I've literally just typed "mkcd" and
walked away for awhile, then come back later to retrieve & label with my
Sharpe magic marker.  In fact, I did 3 the other night while watching
Patriot Games. :-)

By using "tar -czlf /laptop/cd/next/FS.tgz FS", I can backup my entire
system (except for /home) on a single CD.  I'm truely amazed at how well
it works!

I've only done data CDs so far, but given how easy they were, how hard
can audio ones be?  (he asks naively :-)

Kevin

========================
Note:  I have a *big* partition where I copy files from my laptop for
backups.  I use that as a staging area for creating the CD.  Also, I
have 1G FAT partition mounted as /dosh for intermediate output (I use
the same area for burning under WinNT, when I must be there. :-)  So
/laptop/cd/next contains the next set to be burned.  When I need to do
multiple disks, I just create /laptop/cd/next2, copy whatever I need in
there while the first is burning, then rename the dir when ready.  I
strongly suggest you read the man page for cdrecord.  It's got a lot of
useful information there.


#!/bin/bash
# run this as root
set -x

stage1=/laptop/cd/next
stage2=/dosh
rawfile="$stage2/cdimage.raw"

# options that may be useful to us:
# -v  verbose, tell us what it's doing
# -l  allow 32 char filenames
# -J  generate Joliet filenames
# -L  allow filenames to begin with a .
# -T  generate TRANS.TBL, a file in each dir to  help establish the
correct file names
# -A "string"  what to put in the application identifier area, 128 chars
# -p "string"  what to put in the preparer area, 128 chars
# -P "string"  what to put in the publisher area, 128 chars
# -V "string"  what to put in the volume identifer area, 32 chars
# must have -R & -o <file>
mkisofs -v -l -J -L -R -o $rawfile $stage1
ls -l $rawfile

# assuming /mnt is an empty dir for a mount point!
# we can look at the image by doing:
#   mount $rawfile -r -t iso9660 -o loop /mnt
#   ls -R /mnt
#   umount /mnt

# to test without burning (you should do this the first time or two)
# change the speed down to 2 if you only have 2x burn capability,
#   my CDRW disks require that
# change the -dev arg to whatever is appropriate for you!
# cdrecord -v -dummy -fs=6m -dev=0,3,0 -speed=4 -data $rawfile

cdrecord -v -fs=6m -dev=0,3,0 -speed=4 -data $rawfile




More information about the Discuss mailing list