[Dnsmasq-discuss] ProxyDHCP mode is broken for serving ipxe.efi to UEFI pxe clents

[Dreamcat4]

On Sun, May 8, 2016 at 3:41 PM, <wkitty42 at gmail.com> wrote:

> how about going the other way... reverse the logic so that those two are
> skipped all the time... then only if they are needed, add an option to
> enable them...
>
>   pxe-add-menu=X86-64_EFI
>   pxe-add-menu=BC_EFI
>

Yeah that is not an unwelcome suggestion. Actually I was originally going
to say that same thing myself. Unfortunately, looking more closely a
similar type of problems comes up with doing it like that (either way
around).

AFAIKT...

people should only need to care / override this option if the client is
mis-behaving (client cannot show menu / hangs on menu / is buggy). So doing
a positive logic (pxe-add-menu=) is also not elegant. In fact, then there
may be even more default cases to specify and set. (a majority of working
clients).

Well if we must hard-code some behaviour, then for the fewest exception
cases is better, no? Well that seems to be for skip (not add). Because
people come here scratching out heads why pxe menu does not work for UEFI
clients. That is why skip-menu direction was chosen by Jarek. Perhaps
others can comment.


Anyhow regardless whether the direction is add or skip... that is apart
from my previous question. Which is:

Is it not best? (and simplest!) to modify Jarek's patch in this following
ways:

pxe-skip-menu="<CSA1>,<CSA2>,etc"

With a quiet *default* setting of:

pxe-skip-menu="X86-64_EFI,BC_EFI"

+ document it.


That user can clear with:

pxe-skip-menu=""

If they ever need.



Instead of:

pxe-skip-menu=CSA1
pxe-skip-menu=CSA2

Or:

pxe-add-menu=PC-DOS

Many thanks.



Kind Regards
Dreamcat4
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20160508/90af8478/attachment.html>