Syslinux - Sep 2013 - One DHCP/PXE config for BIOS, EFI32, and EFI64 clients?

On 09/26/2013 01:44 AM, Jeffrey Hutzelman wrote:
> Yes; you can configure your DHCP server to hand out different values for
> the pxelinux.configfile option to specific clients, matching on MAC
> address or a variety of other conditions.  Of course, this means that
> the config file for that machine will need to know what firmware to
> expect and thus what path to set.
Hi Jeffrey,
Thanks. I think what the solution is as I mentioned in the thread beginning,
http://www.syslinux.org/archives/2013-September/020848.html
Or did I miss something?
My actual idea is, is that possible we could have an option, even with:
==============================option pxelinux.configfile
"pxelinux.cfg/bios";
==============================this option still lets pxelinux still honor the
rules:
pxelinux.cfg/01-88-99-aa-bb-cc-dd
pxelinux.cfg/C000025B
pxelinux.cfg/C000025
pxelinux.cfg/C00002
pxelinux.cfg/C0000
pxelinux.cfg/C000
pxelinux.cfg/C00
pxelinux.cfg/C0
pxelinux.cfg/C
pxelinux.cfg/default
If such an option exists, it will be very useful because one DHCP/PXE
config could for all BIOS, EFI32, and EFI64 clients.
Thanks in advance.

Steven.
-- 
Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan.
http://www.nchc.org.tw
Public Key Server PGP Key ID: 4096R/47CF935C
Fingerprint: 0240 1FEB 695D 7112 62F0  8796 11C1 12DA 47CF 935C

On Thu, 2013-09-26 at 15:39 +0800, Steven Shiau wrote:
> 
> On 09/26/2013 01:44 AM, Jeffrey Hutzelman wrote:
> > Yes; you can configure your DHCP server to hand out different values
for
> > the pxelinux.configfile option to specific clients, matching on MAC
> > address or a variety of other conditions.  Of course, this means that
> > the config file for that machine will need to know what firmware to
> > expect and thus what path to set.
> Hi Jeffrey,
> Thanks. I think what the solution is as I mentioned in the thread
beginning,
> http://www.syslinux.org/archives/2013-September/020848.html
> Or did I miss something?
> My actual idea is, is that possible we could have an option, even with:
Right; you've asked for a feature that doesn't exist.  I've given
you an
alternative approach you can use with your existing DHCP server that
does not require any new features in Syslinux

On 09/26/2013 02:02 PM, Jeffrey Hutzelman wrote:
> 
> Right; you've asked for a feature that doesn't exist.  I've
given you an
> alternative approach you can use with your existing DHCP server that
> does not require any new features in Syslinux
> 
It wouldn't be too hard to implement, just a matter of someone finding
the time.

	-hpa

On 2013/9/27 ?? 05:02, Jeffrey Hutzelman wrote:
> Right; you've asked for a feature that doesn't exist.  I've
given you an
> alternative approach you can use with your existing DHCP server that
> does not require any new features in Syslinux
Got it. Appreciate that.

Steven.
-- 
Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan.
http://www.nchc.org.tw
Public Key Server PGP Key ID: 4096R/47CF935C
Fingerprint: 0240 1FEB 695D 7112 62F0  8796 11C1 12DA 47CF 935C