[syslinux] syslinux et al misbehave severely when BOOT_IMAGE= is present on append-line already

[Andreas Kotes]

Hello hpa,

* H. Peter Anvin <hpa at zytor.com> [20070112 20:56]:
> >SSIA - when syslinux sees 'BOOT_IMAGE=' on the append line, something
> >seems to go terribly wrong (didn't investigate in detail). You don't
> >even get to see a boot-prompt, even if you try to force it.
> >
> >pxelinux shows the same problem, so I figure it's something generic in
> >the config parser ...
> 
> Please give a copy of your config file.  Syslinux wouldn't even notice 
> the BOOT_IMAGE= on an append line, so something else is wrong.

okay, then it's most likely the extra long commandline (the kernel was
patched to accept it) ...

Thanks for looking into it,

   Andreas

config file (content obfuscated, length kept):

DEFAULT filename
# Message
SAY ******************************************
SAY ** bugme filename - local configuration **
SAY ******************************************

# Kernels
LABEL filename
  KERNEL filename.lnx
  APPEND root=/dev/ram0 initrd=filename.img ip=dhcp ntp_1=172.16.80.3 ntp_2=172.16.80.4 log_status=udp("239.192.70.1") log_syslog=udp("239.192.70.2") log_access=udp("239.192.70.3") log_error=udp("239.192.70.4") log_timings=udp("239.192.70.5") log_forensic=udp("239.192.70.6") snmp_rwcommunity=XXXXXXXXXXXXXXXXXXXXXXXX snmp_rocommunity=YYYYYYYYYYYYYYYYYYYYYYYY snmp_trap_1=172.16.80.3 snmp_trap_2=172.16.80.4 tftp_server=172.16.80.1 upstream=rsync://172.16.80.3/data errordocument=http://www.botherme.com/ BOOT_IMAGE=filename.lnx

-- 
"The problem is not how to wipe out all differences, but how to unite with all
differences intact" -- Tagore
"God is a comedian playing to an audience too afraid to laugh." -- H.L.Mencken