search for: 020848

...p/ftp/http dir. Then these 2 issues could be solved: 1. File name extension matches to its arch. 2. We could handle BIOS and EFI clients in one server, i.e. make the goal of "One DHCP/PXE config for BIOS, EFI32, and EFI64 clients": http://www.syslinux.org/archives/2013-September/020848.html Or maybe there are some key reasons I have missed so we can not have this? My 2 cents. Thanks. Steven. -- Steven Shiau <steven _at_ stevenshiau org> Public Key Server PGP Key ID: 4096R/47CF935C Fingerprint: 0240 1FEB 695D 7112 62F0 8796 11C1 12DA 47CF 935C

...y 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-9...

...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 cours...

...f 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 feature...

...Then these 2 issues could be solved: > 1. File name extension matches to its arch. > 2. We could handle BIOS and EFI clients in one server, i.e. > make the goal of "One DHCP/PXE config for BIOS, EFI32, and EFI64 clients": > http://www.syslinux.org/archives/2013-September/020848.html 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_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...

Dear all, I'd like to have a DHCP/PXE server for different arch of clients, i.e. BIOS, EFI32, and EFI64 clients. As described here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 What Daniel has proposed (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589#10) should work, i.e. Using a file called pxelinux.cfg/bios containing the following 2 lines: