On Thu, 31 Aug 2000, Robert Woten wrote:
>My associate and I have managed to create no less than a dozen new
>coasters for our cafeteria trying to make a backup copy of the Solaris 8
>Installation (Boot) CDROMs.
When experimenting with new burns, CDRW's are invaluable and cost
saving. The cost of a CDR here is $3, the cost of an eraseable
CDRW here is $3.50. I can order them from Toronto for $20 a box
of ten...
So cost of CDRW is no concern nowadays.
>Clearly, it should not be so keenly difficult to make a simple CD copy.
It isn't in general.
>The bulk of our shiny new coasters were the result of following the
>"ftp.fokus.gmd.de:pub/unix/cdrecord/README.sparcboot" instructions
>and then using `cdrecord`
>
>However, for the following bit:
>
>mkisofs -R -sparc-boot sun4,sun4c,sun4m,sun4d,sun4e -o boot.img /mnt/install
>
>we had to presume that "/mnt/install" was the boot disk /dev/dsk/c0t6d0s1
>partition mounted as /mnt/install. Anything else resulted in an error
>with the "mkisofs" command.
If you're merely copying the CDROM's why are you using mkisofs at
all? Use "dd" or "mydd" that comes with cdrecord/whatever and
make an iso image, then burn it.
>Also, unless we used the "fstyp -v" suggestion, the resulting output of
>"mkisofs" was always about 900 megabytes necessitating the
>
>dd if=/dev/dsk/c0t6d0s[1-5] of=sun4[cmde] bs=1k count=[size]
>
>command for each partition.
>
>For the cdrecord aspect, we used:
>
>cdrecord -data -v -dev=6,0 speed=[1246] boot.img
>cdrecord -isofs -data -v -dev=6,0 speed=[1246] boot.img
>(and other combinations that ended up with more immediate disaster)
That all sounds way overly complicated to me. I copy ISO images
in Linux all the time and it is a snap. Doesn't matter if it
were Linux or BSD or something else though, as the software is
the same: cdrecord/dd, etc..
>With such seemingly advanced tools as "cdrecord" and "mkisofs", one could
>easily imagine that copying a damned Solaris 8 boot CDROM would be a
>simple and easy task.
It is if you do it correctly. Sounds like you are trying to
completely remaster the CD. Why?
>However, we not only found out the exact opposite, but also
>that no one else seems to have actually done it successfully
>either (at least according to dejanews and other search
>engines).
While I've not personally copied that particular CD, I do know
people who have, and they copied it as if it were any other CD
with no trouble. The thing is that it was "copied", and copying
the files to the hard disk and remastering, is "remastering", not
"copying".
>The closest we've ever heard of such a copy actually working
>were completely ambiguous "teasers" (conclusively). Such as
>the infamous one liner from Casper Dik "Use dd and cdrecord"
Casper Dik sounds like a wise man. If you attack people that
attempt to help you though, you'll likely get told to take a
hike.
>Thus I seek help from the list to please, please prove us both the
>fools we have been made by this mess.
Well, the info you've been given to use dd and cdrecord is
enough. If you can't get it to work, then you should ask for
more help politely. Attacking people helping you is going to get
you a lot more frisbees. If someone attacked me after giving
help, I might be prone to give them bad instructions just solely
so that they DO make some frisbees.
Relax, take a deep breath, and read the documentation. If you
can't cope with commandline tools, then get XCDroast, or one of
the other GUI frontends. They let you copy CD's at the click of
a mouse. Send your flames to /dev/null though. Nobody here gets
paid money to solve peoples problems while getting blasted.
TTYL
--
Mike A. Harris Linux advocate
Computer Consultant GNU advocate
Capslock Consulting Open Source advocate
Are you an open source developer? Need web space? Your own project mailing
lists? Bug tracking software? CVS Repository? Build environments?
Head over to http://sourceforge.net for all of that, and more, for free!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
