Fork of ipxe; additional commands and features https://git.openslx.org/openslx-ng/ipxe.git/atom/src/include?h=v0.9.5 2008-09-26T02:39:17+00:00 2008-09-26T02:39:17+00:00 Michael Brown 2008-09-26T02:39:17+00:00 urn:sha1:e2d5788716684889a4ea5548942e206414c06bbd 2008-09-25T00:35:15+00:00 Michael Brown 2008-09-25T00:35:15+00:00 urn:sha1:aa8d97258154216896567a901156e7ef4eef399f 2008-09-24T06:21:47+00:00 Michael Brown 2008-09-24T06:21:47+00:00 urn:sha1:b350b10b35760be54d216ef06f8608be05728033 2008-08-28T22:52:19+00:00 Daniel Verkamp 2008-08-28T22:52:19+00:00 urn:sha1:e8b22f203ffe4ae11b654f758270790a2e5e11f1 2008-08-20T02:21:37+00:00 Michael Brown 2008-08-20T02:21:37+00:00 urn:sha1:30fb3b3810409a4971adf9abf00e0842f88d87d8 Determine the network-layer packet type and fill it in for UNDI clients. This is required by some NBPs such as emBoot's winBoot/i. This change requires refactoring the link-layer portions of the gPXE netdevice API, so that it becomes possible to strip the link-layer header without passing the packet up the network stack. 2008-08-18T06:17:41+00:00 Michael Brown 2008-08-18T06:14:27+00:00 urn:sha1:320b072c7a599fe1dab2774f030dd0bedef6f047 Allow for an arbitrary number of splits of the system memory map via INT 15,e820. Features of the new map-mangling algorithm include: Supports random access to e820 map entries. Requires only sequential access support from the underlying e820 map, even if our caller uses random access. Empty regions will always be stripped. Always terminates with %ebx=0, even if the underlying map terminates with CF=1. Allows for an arbitrary number of hidden regions, with underlying regions split into as many subregions as necessary. Total size increase to achieve this is 193 bytes. 2008-08-12T00:05:26+00:00 Andrew Schran 2008-08-12T00:05:26+00:00 urn:sha1:ff2b6a512d7a4f351e48dc9a042099a1010342a3 New min_timeout and max_timeout fields in struct retry_timer allow users of this timer to set their own desired minimum and maximum timeouts, without being constrained to a single global minimum and maximum. Users of the timer can still elect to use the default global values by leaving the min_timeout and max_timeout fields as 0. 2008-08-11T02:43:12+00:00 Michael Brown 2008-08-11T02:12:38+00:00 urn:sha1:5d4839b577e6b6836bd4828ab3ab5d7d2f5ae779 Allow initiator to verify target authentication using CHAP. 2008-08-11T01:31:14+00:00 Michael Brown 2008-08-11T01:30:46+00:00 urn:sha1:7ad2f652b4b19cc8e40f32bb4235b5b5ed60e2ab 2008-07-31T15:55:46+00:00 Michael Brown 2008-07-31T15:55:46+00:00 urn:sha1:481a21798daf0a805f048cabb65f3a80fc60fd06 When we boot from a DHCP-supplied filename, we previously relied on the fact that the current working URI is set to tftp://[next-server]/ in order to resolve the filename into a full tftp:// URI. However, this process will eliminate the distinction between filenames with and without initial slashes: cwuri="tftp://10.0.0.1/" filename="vmlinuz" => URI="tftp://10.0.0.1/vmlinuz" cwuri="tftp://10.0.0.1/" filename="/vmlinuz" => URI="tftp://10.0.0.1/vmlinuz" This distinction is important for some TFTP servers. We now explicitly construct a string of the form "tftp://[next-server]/filename" so that a filename with an initial slash will result in a URI containing a double-slash, e.g. "tftp://10.0.0.1//vmlinuz" The TFTP code always strips a single initial slash, and so ends up presenting the correct path to the server. URIs entered explicitly by users at the command line must include a double slash if they want an initial slash presented to the TFTP server: "kernel tftp://10.0.0.1/vmlinuz" => filename="vmlinuz" "kernel tftp://10.0.0.1//vmlinuz" => filename="/vmlinuz"