Subject: Re: ydl-cs1_2-install.iso
From: Charles Lepple (charles@ghz.cc)
Date: Wed Apr 04 2001 - 15:31:06 MDT
--On Wednesday, April 04, 2001 3:41 PM -0500 Chris Ruprecht
<cruprech@compucom.com> wrote:
> I have to admit, I have not done this myself and I do not know which
> format the .iso image is in. It might be in dd format which is just the
> raw data - not sure how one would convert this into a CD under MacOS.
> Under UNIX/Linux, I'd dd this onto some read/writeable media (CD-RW
> maybe?) und them use Toast to make the final CD ...
The whole idea of an .iso image is that it _is_ what you get from using
'dd' or some similar program to read a CD.
The one-step solution under Linux is to use cdrecord (or one of the many
graphical frontends for it) to burn the image directly to a CD-R. (No need
to put it on a CD-RW, unless I'm missing something.)
I recall burning an ISO image under MacOS about two years ago. It seems
that the program I used (something by Adaptec, I think) didn't recognize
ISO images unless it had written them itself (creator/type problems). I got
around this by creating a dummy ISO image from within that program, using
ResEdit to grab the creator and type from the dummy image, and setting the
creator/type on the downloaded ISO image.
For the curious, it's a whole lot easier to have the CD filesystem be
something more Unix-y (like ISO-9660 + Rock Ridge, which is IIRC what the
install CD is) as opposed to trying to read an HFS CD from Linux. With
ISO-9660 and the Rock Ridge extensions, you get long filenames, symbolic
links and Unix file attributes. When you mount the CD in MacOS, you do get
the long filenames, but that's because the CD is a hybrid HFS/ISO image.
(See misc/CD/mkINSTALLCD on the install CD for more details.)
-- Charles Lepple <charles@ghz.cc> http://ghz.cc/charles/
This archive was generated by hypermail 2a24 : Wed Apr 04 2001 - 15:33:51 MDT