Syslinux - Nov 2009 - IPAPPEND breaks menu module

Just spent a few hours going mad(der) wondering why my menu config
wasn't working.

It looks like the change in 3.74 ("Add IPAPPEND to com32 modules,
especially needed for linux.c32") breaks menu.c32 (and possibly other
modules) since they aren't expecting it.

In particular menu.c32 uses that as an optional menu file, it then
complains "Initial menu has no LABEL entries!" (note that this
isn't
the same as another bug which was fixed w.r.t menu initialisation).
Running v3.83.

Minimal config to reproduce the problem:
UI menu.c32 
IPAPPEND 3

LABEL localboot

(Just stick a "#" in front of IPAPPEND and it all works again)

Thanks

PS: I'm not subscribed but will be checking the archives :-)

Adrian
-- 
bitcube.co.uk - Linux infrastructure consultancy
Puppet, Debian, Red Hat, Ubuntu, CentOS, ...

On 11/25/2009 11:47 AM, Adrian Bridgett wrote:
> Just spent a few hours going mad(der) wondering why my menu config
> wasn't working.
> 
> It looks like the change in 3.74 ("Add IPAPPEND to com32 modules,
> especially needed for linux.c32") breaks menu.c32 (and possibly other
> modules) since they aren't expecting it.
> 
> In particular menu.c32 uses that as an optional menu file, it then
> complains "Initial menu has no LABEL entries!" (note that this
isn't
> the same as another bug which was fixed w.r.t menu initialisation).
> Running v3.83.
> 
> Minimal config to reproduce the problem:
> UI menu.c32 
> IPAPPEND 3
> 
> LABEL localboot
> 
> (Just stick a "#" in front of IPAPPEND and it all works again)
> 
> Thanks
> 
> PS: I'm not subscribed but will be checking the archives :-)
Okay... not many people use a global IPAPPEND, so I can see how that
would break things.

Perhaps the right answer is to not add it to the command line, but make
it possible for the com32 module to do it itself.

	-hpa

On Wed Nov 25 13:45:07 PST 2009, H. Peter Anvin wrote:
> On Wed, Nov 25, 2009 at 19:47:12 +0000 (+0000), Adrian Bridgett wrote:
[snip]
> > Minimal config to reproduce the problem:
> > UI menu.c32 
> > IPAPPEND 3
>
> Okay... not many people use a global IPAPPEND, so I can see how that
> would break things
Most of my entries are "boot this linux kernel" and it's useful
there
(namely so that installers can figure out what NIC to DHCP out of for
machines with multiple NICs).  Only a few are non-linux - I'm not
complaining, just stating my use case :-)

There is a workaround I've discovered - using "UI menu.c32 ~"
allows
it to work nicely.

Thanks,

Adrian
-- 
bitcube.co.uk - Linux infrastructure consultancy
Puppet, Debian, Red Hat, Ubuntu, CentOS, ...