[syslinux] Best way to deal with an idiosyncracy of Intel Boot Agent (IBA)...

Spike White spikewhitetx at gmail.com
Wed Mar 19 15:54:15 PDT 2014

H. Peter,

Do you still work at Intel?  Any pull with Intel's NIC F/W team?
Ask them to "Respect the RFC!"

(Like Cartman -- "Respect My Authority!")

That would be the best solution. :-)

But I know I work for a hardware vendor and I have *zero* pull
with any internal firmware team.


> Date: Tue, 18 Mar 2014 12:02:54 -0700
> From: "H. Peter Anvin" <hpa at zytor.com>
> To: Jeffrey Hutzelman <jhutz at cmu.edu>, Spike White
>         <spikewhitetx at gmail.com>
> Cc: syslinux at zytor.com
> Subject: Re: [syslinux] Best way to deal with an idiosyncracy of Intel
>         Boot Agent (IBA)...
> Message-ID: <5328985E.4020808 at zytor.com>
> Content-Type: text/plain; charset=UTF-8
> On 03/17/2014 10:51 PM, Jeffrey Hutzelman wrote:
> >
> > Another possibility, if you have some control over options generation,
> > is to immediately follow the filename option with a NOOP, which is tag 0
> > and has no length.  This is not included in the option length, but I
> > expect the broken PXE stack will do the expected thing.
> >
> This would almost certainly be the best option.  However, if you can't
> get the filename into the filename field in the first place I expect
> you're not going to be able to get control at this level.
>         -hpa

More information about the Syslinux mailing list