Multiple ks.cfg's on a single boot media?

[Daniel Segall]

I can't seem to make this work right. My CD boots up correctly, and I get
my menu (boot.msg). However, whenever I try to select any of my images, I
just get an error stating it could not find vmlinuz-whatever. My
isolinux.cfg looks like this:

label Rescue
        kernel vmlinuz-RHES-4-U1
        append initrd=initrd-RHES-4-U1.img rescue ks=cdrom:/rescue.ks.cfg
text devfs=nomount ramdisk=10240 vga=0xF01
label RHES-3
        kernel vmlinuz-RHES-3-U5
        append initrd=initrd-RHES-3-U5.img ks=cdrom:/RHES-3-U5-ks.cfg
label RHES-4
        kernel vmlinuz-RHES-4-U1
        append initrd=initrd-RHES-4-U1.img
ks=cdrom:/kickstart/RHES-4-U1-ks.cfg
label FC-4
        kernel vmlinuz-FC-4
        append initrd=initrd-FC-4.img ks=cdrom:/FC-4-ks.cfg

I started with the boot.iso from FC4, and added all of my vmlinuz images
from each version, and my various ks.cfg's. I made a test option, using
the vmlinuz image that was on the original FC4 boot.iso with the following
options, and it works as expected.

label test
        kernel vmlinuz
        append initrd=initrd.img ks=cdrom:/FC-4-ks.cfg


Any ideas why it can't find anything but vmlinuz?

Thanks,
-Dan


On Fri, September 30, 2005 11:19 am, Robert Wehner said:
> On 9/30/05, Daniel Segall <dan at half-asleep.com> wrote:
>> Hey Guys,
>>
>> I am experimenting with moving my pxe based kickstart system to a
>> bootable
>> media/network install. Currently I have my kickstart server on a private
>> network, with everything centrally located on that server. I then
>> connect
>> servers to that network and boot them into pxe, where my menu of images
>> will pop up. This works great, but it's a pain in the ass because I have
>> to physically connect all of the systems to my network in order to kick
>> them.
>>
>> What I would like to do is setup a cd containing all of my boot images,
>> kickstart configs, post install scripts, etc. Then just do http installs
>> over the public network. I know how to create the boot iso with
>> everything, but i'm not sure how to specify the individual ks.cfg's for
>> each image in the isolinux.cfg. With a single config, I could just use
>> ks=cdrom. Is it possible to use a path with this?
>
> It is possible. I update the isolinux.cfg file to append extra stanzas
> for each ks.cfg on the CD. Something like:
>
> label webserver
>   kernel vmlinuz
>   append initrd=initrd.img ks=cdrom:/webserver.ks.cfg
> label database
>   kernel vmlinuz
>   append initrd=initrd.img ks=cdrom:/database.ks.cfg
>
> At the boot prompt the user just types in 'database' or 'webserver' to
> get the correct config. they type nothing if they want an interactive
> install.
>
> --
> ----
> Robert Wehner
> rwehner at gmail.com
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
>