Depending on the complexity of the options you have two options. One is
used in "complex.com" example, where the user has checkboxes and radio
options to control parameters to pass to the kernel. This case requires
a handler (for an example see complex.com).
If you have only a few scenarios (say under 8) of options to pass to
ks.menu, you can just make "Custom Valhalla" a submenu, and have the 8
possibilities in that submenu. Something like this
rhsubmenu = add_menu(....)
choicea =
add_item("<F>","first",OPT_RUN,"PXELINUX_LABEL
p=q r=s",0)
choicea =
add_item("<S>","seond",OPT_RUN,"PXELINUX_LABEL
a=b c=d",0)
choicea =
add_item("<T>","third",OPT_RUN,"PXELINUX_LABEL
h=i j=k",0)
....
mainmenu = add_menu(...)
add_item("RH Menu","RH",OPT_SUBMENU,rhsubmenu)
- Murali
Virgil wrote:> Hi all,
>
> I'm looking for some menu examples for Murali's menu system.
> Specifically, a headstart on creating a Kickstart menu which covers the
> most common options with the intention of creating this:
>
>
> label ks.menu
> kernel vmlinuz.ks.$DIST
> append ksdevice=eth0
> ks=http://kickstartserver/$DIST/Custom/ks.cfg.$DIST
> initrd=initrd.ks.$DIST lang= devfs=nomount ramdisk_size=8192
>
>
> Hmm...looking at it, that's not much more than a single OPT_RADIOMENU.
>
> valhalla = add_item("Custom <V>alhalla","WC Customised
RedHat
> 7.3",OPT_RADIOITEM,"valhalla",0);
> add_sep();
> startks = add_item("Start <K>ickstart","Start RedHat
Kickstart
> install",OPT_RUN,"ks.menu",0);
>
> But then I'll need to a handler to append all the options.
>
> valhalla->handler = &dist_handler;
>
> Any advice appreciated. Examples even more :)
>
> Regards,
>
> Virgil
>