On Thu, Feb 4, 2010 at 6:44 PM, Tal Aloni <[email protected]> wrote: > approach #1: > currently, gPXE execute only the first embedded image, we can use additional > embedded images (scripts), one to load each OS, and manually execute them > when needed. [...] > cons: > it's necessary to keep an image up to date with many embedded scripts, > the user would have to rebuild the image every time an OS has been added.
Centralized boot infrastructure solves this problem. The menu.c32/vesamenu.c32 COMBOOT modules are a popular way to implement OS selection, see http://syslinux.zytor.com/wiki/index.php/Menu. gPXE also has PXE menu support, which is the native PXE way of providing OS selection. Adding a new OS involves changing configuration on the server only, clients require no modification. Do you think vesamenu.c32 is a solution for you? Stefan _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
