Comment 11 for bug 270822

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 -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table new_iso

Bad news: isolinux.cfg needs to be patched otherwise the CD triggers a reboot (triple fault?).

gfxboot.com seems to procure the list of labels from isolinux.cfg to gfxboot but doesn't respect
"include" directives: it only parses isolinux.cfg.

Ubuntu's gfxboot script (menuconfig.inc from gfxboot-theme-ubuntu) does the right thing though and
successfully parses all cfg files, but then tries to match the labels provided by the com module
with the labels it has parsed (to set the human readable names). Because of this mismatch, labels
in other config files but isolinux.cfg are not displayed.

The following patch is need to isolinux.cfg (explicitely states labels in isolinux.cfg):

isolinux > diff -du isolinux.cfg.orig isolinux.cfg
--- isolinux.cfg.orig 2009-07-25 08:43:55.000000000 -0700
+++ isolinux.cfg 2009-07-26 20:27:24.000000000 -0700
@@ -2,4 +2,8 @@
 default vesamenu.c32
 prompt 0
 timeout 0
-gfxboot bootlogo
+label install
+label check
+label memtest
+label hd
+ui gfxboot.com bootlogo

Tested all four labels and played with the UI (modes, ...). Worked fine.

It seems that with Syslinux 4, gfxboot scripts won't have to parse configuration files anymore. In the meantime,
gfxboot-theme-ubuntu may need to be patched to avoid the previous hack. Shouldn't be too hard though.