After thinking a bit of the multi-file support in 3.31-pre1, and considering a few users' feedback on the subject, I have made a couple of changes: 1. The dummy filename ~ can be used to mean "the main config file". 2. There is a MENU INCLUDE directive now. -hpa
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 H. Peter Anvin schrieb:> After thinking a bit of the multi-file support in 3.31-pre1, and > considering a few users' feedback on the subject, I have made a > couple of changes: > > 1. The dummy filename ~ can be used to mean "the main config file". > 2. There is a MENU INCLUDE directive now. > > -hpaHi! I like the new vesamenu stuff and the "MENU INCLUDE" option - it simplifies menu setup considerably! However, I found some odd behaviour, that looks like a bug to me: I'm trying to include a "go back to main menu" file: - ---------------------------------------------------------- LABEL mainmenu MENU DEFAULT MENU LABEL ^0 Back to Main Menu KERNEL vesamenu.c32 - ---------------------------------------------------------- in my basic config file: - ---------------------------------------------------------- MENU TITLE DOS Boot Floppies MENU INCLUDE pxelinux.cfg/menu.inc LABEL dos-3com MENU LABEL ^1 DOS 3com Bootfloppy KERNEL memdisk APPEND initrd=/dos/dos_3com.img floppy LABEL novell MENU LABEL ^2 Novell something KERNEL memdisk APPEND initrd=/dos/288_ncp.img MENU INCLUDE pxelinux.cfg/main.inc - ---------------------------------------------------------- I'd expect a menu like: 1 DOS 3com Bootfloppy 2 Novell something 0 Back to Main Menu But I get: 1 DOS 3com Bootfloppy 0 Back to Main Menu 2 Novell something If I move the "MENU INCLUDE" option up and down - it's always the same: It's one position above then intended one. Am I missing something, or may this be a bug in the config file parsing code? Bye, Marcel - -- - ---- Dipl.-Inf. Marcel Ritter Linux/Novell Regionales Rechenzentrum Erlangen Tel: 09131 / 85-29958 E-Mail: Marcel.Ritter at rrze.uni-erlangen.de - ---- Unix _IS_ user friendly... It's just selective about who its friends are. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFE4d5XLTbgg79wMERAuPYAJ4gwyY9Bs4h5n931www1Ub6UKoenwCeMn2n /DOgWcota2Wl49/Xs3tnTpI=GoBS -----END PGP SIGNATURE-----
On 9/22/06, H. Peter Anvin <hpa at zytor.com> wrote:> After thinking a bit of the multi-file support in 3.31-pre1, and > considering a few users' feedback on the subject, I have made a couple > of changes:Reading README.menu I understand we can use "MENU INCLUDE" just for menu system setup, not for adding labels. But in this thread http://syslinux.zytor.com/archives/2006-September/007347.html you answer to an user, which is using "MENU INCLUDE" for adding a common LABEL, like it's something possible and supported. So, can we include LABEL/KERNEL/APPEND statements in a file which is read with "MENU INCLUDE"? Also, assuming that graphics.conf and othermenu.conf don't contain conflicting directives, is using APPEND graphics.conf othermenu.conf 100% equivalent to using APPEND othermenu.conf and then using "MENU INCLUDE graphics.conf" at the top of othermenu.conf? If yes, what's the method you recommend? Thanks -- giulioo at pobox.com