>From the messages it looks like it its trying to import a previous
session?
Make sure you have deleted any previous .iso image files you have
created, also delete any misc/boot/boot.catalog file that has been
created.
Make sure you have plenty of free disk and memory.
Just to recap, the mkisofs line you should use to create a non-bootable
image should be (note the case of the switches):
mkisofs -a -A "RedHat Linux 5.1 with Patches to 17/06/98" -d -L
-o /temp/RH5.iso -P "Publisher ID" -p "Preparer ID" -r -T
-N /temp/rh5
Graham...
Netlink Tech wrote:
>
> Thanks Graham,
>
> I still have a problem though. I still get a seg fault/core dump.
> Same place, without the "Emulating a 1.44 meg floppy" line.
>
> Here is a bit of the core dump:
> --------------------------------------------
> ^@Can't allocate memory for excluded filename
> ^@ Seek error on old image
> ^@**BAD RRVERSION^@NM^@CE^@PX^@TF^@.^@..^@TRANS.TBL^@<translation
> table>^@%c %s
> ^@Previous session must have either Rock Ridge (-R) or
> ^@TRANS.TBL (-T) for mkisofs to be able to correctly
> ^@generate additional sessions.
> ^@rb^@ Read error on old image %s
> ^@CD001^@Should never get here
> ^@/^@Special parameters for cdwrite not specified with -C
> ^@Malformed cdwrite parameters
> ^@Can't exclude RE '%s' - too many entries in table
> ^@Can't allocate memory for excluded filename
> ^@.^@..^@/^@A boot catalog exists and appears corrupted.
> ^@Please check the following file: %s.
> ^@This file must be removed before a bootable CD can be done.
> ^@Error creating boot catalog, exiting...
> ^@^@CD001^@EL TORITO SPECIFICATION^@Uh oh, I cant find the boot catalog!
> ^@Uh oh, I cant find the boot image!
> ^@
> Size of boot image is %d sectors -> ^@Emulating a 1.44 meg floppy
> ^@Emulating a 2.88 meg floppy
> ^@Emulating a 1.2 meg floppy
> ^@
> Error - boot image is not the an allowable size.
> ^@Error opening boot catalog for update.
> ----------------------------------------
>
> I don't know what to make of it yet.
>
> Curt
>
> On Thu, 18 Jun 1998, Graham wrote:
>
> > If you are not bothered about the CD being bootable then just omit the
> > following from the mkisofs command line:
> >
> > -b misc/boot/autoboot.img -c misc/boot/boot.catalog
> >
> > You will then have your ISO image which you can FTP to Windows and burn.
> >
> > Graham...
> >
> > Netlink Tech wrote:
> > >
> > > I successfully download the directory tree for RH5.1.
> > > I replaced the old RPMs with the updated ones.
> > > I verified the structure and made sure that the directory names were
> > > correct.
> > > I made the new hdlist with this command(but with my path):
> > > /temp/rh5/misc/src/install/genhdlist /temp/rh5
> > >
> > > I made sure that mkisofs rpm was installed (RH5.0)
> > > I ran the command (on one line):
> > >
> > > mkisofs -b misc/boot/autoboot.img -c misc/boot/boot.catalog -a -A "RedHat
> > > Linux 5.1 with Patches to 06/12/98" -d -L -o
> > > /home/web/smiller/curts_stuff/rh51/RH5_1.iso -P "Publisher ID" -p
> > > "Preparer ID" -r -T -N /home/web/smiller/curts_stuff/rh51
> > >
> > > .
> > > . <output removed here>
> > > .
> > > Using L.000 for ./rr_moved/l (l)
> > >
> > > Size of boot image is 2880 sectors -> Emulating a 1.44 meg floppy
> > > Total extents scheduled to be written = 184105
> > > Segmentation fault (core dumped)
> > > --------------------------------
> > > I got a Seg fault/core dump using the autoboot.img (copied from my
> > > purchased RH5.0 CD to <my path>/rh51/misc/boot/autoboot.img
> > >
> > > This has got me thinking that the 5.0 autoboot.img will not work with the
> > > 5.1 distribution.
> > >
> > > Question:
> > > I have written a few CDs with my CDROM writer. It is in an NT 4.0
> > > Workstation and the CDs that I made were Win3.1/Win95/WinNT stuff and work
> > > fine.
> > >
> > > I am not really concerned with booting from a CDROM...as long as I can
> > > install from cd with a boot floppy. Is it possible to get
> > > around the autoboot.img issue?
> > >
> > > After mkisofs, will I have a single image that I can ftp to my NT
> > > workstation to burn to the cd?
> > >
> > > Thanks,
> > >
> > > Curt
> > >
> > > On Thu, 18 Jun 1998, Jos Vos wrote:
> > >
> > > > Cheng Yuan-Chung wrote:
> > > >
> > > > > But can anyone tell me that where can I find "autoboot.img"
> > > > > and "boot.catalog" ???
> > > > >
> > > > > I can't find these two files in the misc/boot . :(
> > > >
> > > > The file boot.catalog is created by mkisofs itself, so you don't
> > > > need it (in fact, it's overwtitten if it's already there, I think).
> > > >
> > > > The file autoboot.img is currently not (at least not with that name)
> > > > available in the RH 5.1 tree. We hope someone from RH will tell
> > > > us more about that. You may want to try the autoboot.img file
> > > > from the RH 5.0 tree (dunno if that will work properly, it contains
> > > > another kernel version)
>
> <some more stuff removed>
>
> --
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
> To unsubscribe: mail [EMAIL PROTECTED] with
> "unsubscribe" as the Subject.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
