I am new to SYSLINUX/PXELINUX and it is great! Thanks!
Looking around the archives for uses/examples for the simple menu
(menu.c32) for our implementation (DOS boot with networking support for
various NICs), and it occurred to me that I might want to go back to the
main menu if I ended up in the wrong sub-menu. Also would be useful if
one needed to create multiple levels of menus and wanted to step back up
a level, or back to the top level.
Maybe I missed this in another post, and likely someone has already done
it. But just in case this could help someone else:
So in .\pxelinux.cfg\default pretty standard:
Default menu.c32
prompt 0
TIMEOUT 0
ALLOWOPTIONS 0
NOESCAPE 1
MENU TITLE FaSTLab Boot - NIC Selection
Label intel
MENU LABEL [^I] Intel NICs
kernel menu.c32
append intel_menu.conf
Label 3com
MENU LABEL [^3] 3COM NICs
kernel menu.c32
append 3com_menu.conf
....
Now copy that same default file from the pxelinux.cfg folder to the same
level as pxelinux.0 .
In the sub-menu file (.\intel_menu.conf) the Back to Main label is a
simple call of menu.c32 using the default menu again:
ALLOWOPTIONS 0
NOESCAPE 1
MENU TITLE FaSTLab Boot - Intel NICs
Label intel100
MENU LABEL [^1] Intel 100
kernel memdisk
append initrd=intel100.img
Label intel1000
MENU LABEL [^2] Intel 1000 (really the 100)
kernel memdisk
append initrd=intel100.img
Label main
MENU LABEL [^B] Back to Main Menu
kernel menu.c32
append default
...
Seems to work well.
Is there another way to do this?
Thanks again,
Tim
On 12/15/05, Lentz, Tim <Tim_Lentz at maxtor.com> wrote: [..[> > Maybe I missed this in another post, and likely someone has already done > it. But just in case this could help someone else: > > So in .\pxelinux.cfg\default pretty standard: >[...]> Now copy that same default file from the pxelinux.cfg folder to the same > level as pxelinux.0 . > > In the sub-menu file (.\intel_menu.conf) the Back to Main label is a > simple call of menu.c32 using the default menu again:[..]> > Seems to work well. > Is there another way to do this?Using a complex menu can achieve this. You can really have menus with submenus, see the complex example in the menu subdir of the sources. Hijacking the thread a bit, I noticed that when using pxelinux and putting a entry like this on the append line: append initrd=://dir1/initrd.img other_parameters makes pxelinux requesing the 'pxe-prefix/di1/initrd.img' file instead of the desired behaviour of requesting /dir1/initrd.img'. It works if I modify the line like this: append initrd=tftp_server://dir1/initrd.img other_parameters I tried to track this down but did not succeed in understanding why is this not working, it seems that mangle_name/unmangle_name do their job well, but I still can't understand why it's not working in this particular example. -- mitu
True, the advanced menus look great. But I want to keep this as simple as possible as it will be handed off to lab technicians at some point. They will need the ability to add/modify the menus. So compiling is not the best answer for this implementation: "It requires that the menu is compiled from a simple C file, see menu/simple.c and menu/complex.c for examples."> -----Original Message----- > From: syslinux-bounces at zytor.com > [mailto:syslinux-bounces at zytor.com] On Behalf Of Cristi Mitrana > Sent: Thursday, December 15, 2005 3:07 AM > To: syslinux at zytor.com > Subject: Re: [syslinux] menu.c32 - Return from sub-menu > > On 12/15/05, Lentz, Tim <Tim_Lentz at maxtor.com> wrote: > [..[ > > > > Maybe I missed this in another post, and likely someone has already > > done it. But just in case this could help someone else: > > > > So in .\pxelinux.cfg\default pretty standard: > > > [...] > > Now copy that same default file from the pxelinux.cfg folder to the > > same level as pxelinux.0 . > > > > In the sub-menu file (.\intel_menu.conf) the Back to Main > label is a > > simple call of menu.c32 using the default menu again: > [..] > > > > Seems to work well. > > Is there another way to do this? > > Using a complex menu can achieve this. You can really have > menus with submenus, see the complex example in the menu > subdir of the sources. >...> -- > mitu > > _______________________________________________ > SYSLINUX mailing list > Submissions to SYSLINUX at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > >
Murali Krishnan Ganapathy
2005-Dec-15 22:44 UTC
[syslinux] menu.c32 - Return from sub-menu
I am currently thinking of writing a python script which takes a ini-like file which can declare the menu structure and generate the C code. This will make it easier for people to change the menus, but will not eliminate the need for compilation. Eventually, if I can get the parser implemented in C, then the need for compiling will be eliminated. - Murali Lentz, Tim wrote:>True, the advanced menus look great. > >But I want to keep this as simple as possible as it will be handed off >to lab technicians at some point. They will need the ability to >add/modify the menus. > >So compiling is not the best answer for this implementation: > >"It requires that the menu is compiled from a simple C file, see >menu/simple.c and menu/complex.c for examples." > > > > >>-----Original Message----- >>From: syslinux-bounces at zytor.com >>[mailto:syslinux-bounces at zytor.com] On Behalf Of Cristi Mitrana >>Sent: Thursday, December 15, 2005 3:07 AM >>To: syslinux at zytor.com >>Subject: Re: [syslinux] menu.c32 - Return from sub-menu >> >>On 12/15/05, Lentz, Tim <Tim_Lentz at maxtor.com> wrote: >>[..[ >> >> >>>Maybe I missed this in another post, and likely someone has already >>>done it. But just in case this could help someone else: >>> >>>So in .\pxelinux.cfg\default pretty standard: >>> >>> >>> >> [...] >> >> >>>Now copy that same default file from the pxelinux.cfg folder to the >>>same level as pxelinux.0 . >>> >>>In the sub-menu file (.\intel_menu.conf) the Back to Main >>> >>> >>label is a >> >> >>>simple call of menu.c32 using the default menu again: >>> >>> >>[..] >> >> >>>Seems to work well. >>>Is there another way to do this? >>> >>> >> Using a complex menu can achieve this. You can really have >>menus with submenus, see the complex example in the menu >>subdir of the sources. >> >> >> >... > > >> -- >>mitu >> >>_______________________________________________ >>SYSLINUX mailing list >>Submissions to SYSLINUX at zytor.com >>Unsubscribe or set options at: >>http://www.zytor.com/mailman/listinfo/syslinux >>Please do not send private replies to mailing list traffic. >> >> >> >> > >_______________________________________________ >SYSLINUX mailing list >Submissions to SYSLINUX at zytor.com >Unsubscribe or set options at: >http://www.zytor.com/mailman/listinfo/syslinux >Please do not send private replies to mailing list traffic. > > > >