On Mon, 3 Oct 2005, Daniel Segall wrote: > Date: Mon, 3 Oct 2005 09:35:05 -0400 (EDT) > From: Daniel Segall <dan@xxxxxxxxxxxxxxx> > Reply-To: Discussion list about Kickstart <kickstart-list@xxxxxxxxxx> > To: Discussion list about Kickstart <kickstart-list@xxxxxxxxxx> > Subject: Re: Multiple ks.cfg's on a single boot media? > > I spoke too soon. > It still gives me the same error after renaming all of my images and > editing the isolinux.cfg to match: > > boot: Rescue > Could not find kernel image: vmlinuzRHES4U1 > boot: FC-4 > Could not find kernel image: vmlinuzFC4 > > Tried making the names lowercase as well, just to be sure, and I still get > no love. > > Any other thoughts? > > Thanks, > -Dan Please see a quote from http://syslinux.zytor.com/iso.php: Note that ISOLINUX only uses the "plain" ISO 9660 filenames, i.e. it does not support Rock Ridge or Joliet filenames. It can still be used on a disk which uses Rock Ridge and/or Joliet extensions, of course. Under Linux, you can verify the plain filenames by mounting with the "-o norock,nojoliet" option to the mount command. Note, however, that ISOLINUX does support "long" (level 2) ISO 9660 plain filenames, so if compatibility with short-names-only operating systems like MS-DOS is not an issue, you can use the "-l" or "-iso-level 2" option to mkisofs to generate long (up to 31 characters) plain filenames. ISOLINUX does not support discontiguous files, interleaved mode, or logical block and sector sizes other than 2048. This should normally not be a problem. I think this explains your problems. Best regards, Wojtek
