similar to: One DHCP/PXE config for BIOS, EFI32, and EFI64 clients?

> There might be an alternative (and possibly others too): let the user > select the appropriate firmware from within pxelinux.cfg/default. > > So, keep using the same method you used in previous versions, instead > of selecting the Syslinux cfg / firmware from the DHCP snippet that > Daniel posted. > > If you actually get to pxelinux.cfg/default (as you probably used

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 >

On 2014/4/23 ?? 12:54, Ady wrote: > 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 >

> > On 09/20/2013 02:34 AM, Ady wrote: > >> There might be an alternative (and possibly others too): let the user > >> select the appropriate firmware from within pxelinux.cfg/default. > >> > >> So, keep using the same method you used in previous versions, instead > >> of selecting the Syslinux cfg / firmware from the DHCP snippet that >

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

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,

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has,

On 04/23/2014 05:27 PM, Ady wrote: > OK then, so let's review the situation a little more accurately. > > _ Goal: to be able to keep 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 >

> > > On 2014/4/23 12:54, Ady wrote: > > 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 > >

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

Hi Everyone. is there a need to have on searching the configuration file the request for the "odd ip addresses" ? Let me explain: from /doc/pxelinux.txt : ... Next, it will search for the config file using its own IP address in upper case hexadecimal, e.g. 192.0.2.91 -> C000025B (you can use the included progam "gethostip" to compute the hexadecimal IP address for

Hi! As documented: http://www.syslinux.org/wiki/index.php/PXELINUX When pxelinux "boots" it is looking for this: /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd /mybootdir/pxelinux.cfg/C000025B /mybootdir/pxelinux.cfg/C000025 /mybootdir/pxelinux.cfg/C00002 /mybootdir/pxelinux.cfg/C0000 /mybootdir/pxelinux.cfg/C000

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

On 10/16/2013 06:23 PM, Steven Shiau wrote: > > > On 2013/9/27 ?? 07:28, H. Peter Anvin wrote: >> It wouldn't be too hard to implement, just a matter of someone finding >> the time. >> >> -hpa > > Great! I believe this feature is very useful for a PXE server. > Since syslinux 6.02 is released, may we expect this feature to be added > in 6.03?

On 09/20/2013 02:34 AM, Ady wrote: >> There might be an alternative (and possibly others too): let the user >> select the appropriate firmware from within pxelinux.cfg/default. >> >> So, keep using the same method you used in previous versions, instead >> of selecting the Syslinux cfg / firmware from the DHCP snippet that >> Daniel posted. >> >>

I intend to release SYSLINUX 3.73-pre7 as SYSLINUX 3.73 as soon as possible. Please let me know if there are any outstanding bugs with 3.73-pre7 that either haven't been reported or I have forgotten about... it's been a while. -hpa

Hello! I have some weird problem. I have pxelinux(3.10) configured fine. Os: FreeBsd 6.1, tftp-hpa 0.41, some version of dhcpd from ports. It worked before on another machine which's hd passed away and i lost my working example. Configured new computer as boot server... What happends is dhcp gives all the parameters to client(this server also works for giving addresses to workstations) -

On 2014?03?07? 18:24, Ady wrote: > Hi Steven, > > Perhaps this could be of some basic sample/help, being based on > Debian: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > > where: > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe. > _ lpxelinux.0 (from official Syslinux archive) could optionally be > added. > > _ from the

On 04/23/2014 09:06 PM, Ady wrote: > Suggestions and patches are surely welcome. Ady, Mine is only suggestion, and for sure I will just follow what Syslinux developers decide. 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

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