About the crash when no label is specified: it seems actually that
gfxboot core never runs menuconfig.init (the menu parsing function).
Running under Bochs, it appears that gfxboot core does its initialization
(gfx_init_51 is run since the hello msg is displayed) and the VGA
initialization too (
Patching gfxboot-theme-ubuntu to make it parse labels that are not in
isolinux.cfg was indeed easy.
The tough part is to fix the bug that makes gfxboot crash if no label is
specified in isolinux.cfg (my patch still requires a dummy foo label).
Couldn't find the problem. I may need some help on tha
Tested with Karmic Alpha 2 ISO (still downloading Alpha 3) and a nightly
Karmic chroot as build environment.
Testing Done: updated isolinux.bin and vesamenu.c32 with the ones built in my
PPA. Added gfxboot.com.
Built with: sudo mkisofs -r -V 'Ubuntu 9.10 i386' -o
karmic-alternate-i386-hacked.iso
Did a first pass on the merge with some basic testing (extlinux and
vesamenu.c32 on hp2530p).
Among major changes is the deletion of the gfxboot patches: an upstream
version is available as a com16 module. This has some impact on
configuration files. I am still trying to figure out how the officia
