Hi all, I'm in need of creating a simple menu where two options must be available: 1) (default) Boot from local harddrive 2) start installation 2) option should display a simple text disclaimer and if agreed it then would ask for a number from 32 to 254 which is then appended to one of commandline parameters. I have quite a lot of experience with [sys|pxe|iso]linux and some programming skills. We're currently using the simple graphical menu, where those two options already exist although without the disclamer and the new question for the user. This is a snippet of our current ISOLINUX file: label vesa menu label Iniciar a instalacao kernel vmlinuz append quiet initrd=initrd.img text acpi=off ks=http://installserver/scripts/kickstart.php append noipv6 The end result we hope to achive is to make our kickstart installtion even better by supplying an additional parameter to the dynamic kickstart.php file. Something along the lines of (the number 123 was provided by the user): label vesa menu label Iniciar a instalacao kernel vmlinuz append quiet initrd=initrd.img text acpi=off ks=http://installserver/scripts/kickstart.php?123 append noipv6 I humbly accept any insight or guidelines, and if we need to create some code, my employer would be willing to provide that code back to the community. thank you in advance, Luis Correia
Luis.F.Correia wrote:> Hi all, > > I'm in need of creating a simple menu where two options must be available: > > 1) (default) Boot from local harddrive > 2) start installation > > 2) option should display a simple text disclaimer and if agreed it then > would ask for a number from 32 to 254 which is then appended to one of > commandline parameters. > > I have quite a lot of experience with [sys|pxe|iso]linux and some > programming skills. > We're currently using the simple graphical menu, where those two options > already exist although without the disclamer and the new question for the > user. >You might be able to do it with the complex menu system; otherwise you'd probably have to modify the (simple) menu system -- you can use the password-entry dialog box routine as a model. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
Hi H.Peter,> -----Original Message----- > > You might be able to do it with the complex menu system; > otherwise you'd probably have to modify the (simple) menu > system -- you can use the password-entry dialog box routine > as a model.My intention is starting up with the code from vesamenu (which is pretty), and add all needed code. But I've now seen that the menu code from Murali and the vesa have different structures. Although it shouldn't be that hard to do, should I create a new folder under com32 and copy all files from there, adjusting what I need or do you have a better suggestion? On a related subject, are there any funcions to manipulate the append line that is passed?> > -hpa >Luis Correia
H. Peter, On Thu, May 28, 2009 at 21:42, H. Peter Anvin <hpa at zytor.com> wrote:> Luis Correia wrote: >> >> thanks for all of your inputs. >> >> We have opted for a long help explanation and some screen captures to >> guide the users. >> >> The real need for user input will affect about 15% of the >> installations, so it is bearable. >> > > By the way, given the rather small number of possibilities you have to > deal with, you could also just make a really long menu -- possibly a > submenu, and put your disclaimer text as TEXT HELP on the entry to that > submenu. > > ? ? ? ?-hpaYour da men! The idea of having a submenu with all possible options works flawlessly. (it even worked with a large file 41k) To avoid any errors I wrote a script to generate the file. thank you lots of ! Luis Correia