search for: c000025

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 any host.) If that file is not found, it will remove one hex digit and try again. Ultimately, it will try looking for a file named "default" (in lower case). As an exampl...

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 /mybootdir/pxelinux.cfg/C00 /mybootdir/pxelinux.cfg/C0 /mybootdir/pxelinux.cfg/C /mybootdir/pxelinux.cfg/default Is is...

...s boot server... What happends is dhcp gives all the parameters to client(this server also works for giving addresses to workstations) - > seems like pxelinux begins looking for possible config file(something like following): /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 /mybootdir/pxelinux.cfg/C00 /mybootdir/pxelinux.cfg/C0 /mybootdir/pxelinux.cfg/C /mybootdir/pxelinux.cfg/default Delay between each line is about 2-3 minutes. It takes conside...

...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 (?). Yes, the thread is about that. Howe...

...h the following line specified in dhcpd.conf: =============================== option pxelinux.configfile "pxelinux.cfg/bios"; =============================== then only the config file pxelinux.cfg/default will be used. Those file names like: 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 won't be loaded if I want to use some specific config file for some machine. So, is there any method that I can make it so that those config files based on MAC addre...

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

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

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 >

...=UTF-8 On 11/21/2012 06:49 AM, Torgeir.Wulfsberg at kongsberg.com wrote: > > Is is possible to make pxelinux look for MAC and IP, removing one hex digit (or 2 for mac) and try again like this: > > /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd > /mybootdir/pxelinux.cfg/C000025B > /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc > /mybootdir/pxelinux.cfg/C000025 > /mybootdir/pxelinux.cfg/01-88-99-aa-bb > /mybootdir/pxelinux.cfg/C00002 > /mybootdir/pxelinux.cfg/01-88-99-aa > /mybootdir/pxelinux.cfg/C0000 >...

Hi, Is it possible for pxelinux.0 to use the mac address of the machine in addition to IP address and its derivatives from the tftp server? Thanks, -- rajeev _________________________________________________________________ Check out Election 2004 for up-to-date election news, plus voter tools and more! http://special.msn.com/msn/election2004.armx

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

...hcpd.conf: > =============================== > option pxelinux.configfile "pxelinux.cfg/bios"; > =============================== > then only the config file pxelinux.cfg/default will be used. Those file > names like: > 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 > > won't be loaded if I want to use some specific config file for some machine. > > So, is there any method that I can...

...ng? 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....

...nt side. > Or maybe I missed something? > > Regards, > Steven. My focus was on: option pxelinux.configfile "pxelinux.cfg/bios"; and the respective lines for efi32 and efi64, so to try to give you the usual behavior such as: 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 Although you didn't explicitly mention the "unattended client for massive deployment" condition before, I should probably had assumed it. Creating a new c...

> 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

Hi This is what I like to be able to do. 1. Computer boot on LAN, using PXELinux. 2. If the computer is booting for the first time it sends MAC adr, RAM, size of harddrive and name of videocard to a shared folder on a computer, maybe a server, that is attached to the network. 3. If this is not the first time it scan for a new task, could be a new ghostimage or an unattended installation of a

> Check if the first character matches the character to replace, rather > than skipping it and starting with the second. > > Signed-off-by: Josh Triplett <josh at joshtriplett.org> > --- > > I'm assuming, based on a look at the callers, that this is not > intentional, and that it just happened that none of the callers happened > to ever need to replace the

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 > > or some similar paths (perhaps depending on firmware type? or under > sub-directories?) > > _ The usage of sub-dire...