[syslinux] *.c32 for efi64 and efi32?

[Ady]

> 
> On 2014/4/23  09:55, Gene Cumm wrote:
> > The resulting config would require suffix-less module references, i.e.
> > "UI menu" or "COM32 ls".
> >
> > Additionally, I documented the basics of my test system here:
> >
> > http://www.syslinux.org/archives/2014-February/021740.html
> >
> > Bear in mind, by "URL-like file locations", I mean that if we have
> > "bios/pxelinux.0", "efi32/bootia32.efi" and "efi64/bootx64.efi" as
> > paths relative to the root and a common kernel "shared/vmlinuz", you'd
> > use "::shared/vmlinuz" or "tftp://<my-server>/shared/vmlinuz" in your
> > configs instead of "../shared/vmlinuz" (which is prone to issues).
> Because pxelinux.0, bootia32.efi and bootx64.efi are different names, so 
> I can put them in the same path, no problem for this, i.e.
> $ ls -alFh /tftpboot/nbi_img/{*.0,*.efi}
> -rw-r--r-- 1 root root 157K Apr 22 15:30 /tftpboot/nbi_img/bootia32.efi
> -rw-r--r-- 1 root root 160K Apr 22 15:30 /tftpboot/nbi_img/bootx64.efi
> -rw-r--r-- 1 root root 105K Apr 22 15:30 /tftpboot/nbi_img/gpxelinux.0
> -rw-r--r-- 1 root root  74K Apr 22 15:30 /tftpboot/nbi_img/lpxelinux.0
> -rw-r--r-- 1 root root  42K Apr 22 15:30 /tftpboot/nbi_img/pxelinux.0
> 
> My goal is to put all the required COMBOOT files in the same path 
> (/tftpboot/nbi_img/), too. No subdir, so that I can make the goal of 
> "One DHCP/PXE config for BIOS, EFI32, and EFI64 clients":
>     http://www.syslinux.org/archives/2013-September/020848.html
> >
> > Bear in mind, the only chance of a universal Linux kernel binary is
> > with an x86 (32-bit) kernel with BIOS and EFI hooks.  I can't be
> > certain if Syslinux EFI64 can boot such a kernel yet.
> Actually not x86 (32-bit), I use x86-64 kernel from Ubuntu or Debian, 
> and of course, it could boot both on EFI64 or BIOS arches. So I should 
> change the goal as:
> "One DHCP/PXE config for BIOS (legacy PXE boot) and EFI64 (uEFI network 
> boot) clients"
> 
> Thanks!
> 
> Steven.
> 
> -- 
 
Is this about not liking the need for (sub)directories (depending on 
firmware)? Or is it about functionality?

If I understood correctly the prior email threads, the (real) problem 
was in trying to maintain the searching for:

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

with the new DHCP/PXE configurations proposed by Daniel. But maybe I 
got it wrong (?).

Perhaps there is a different (better?) way to deal with all this?

Regards,
Ady.