<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openslx-ng/ipxe.git/src/usr, branch v0.9.5</title>
<subtitle>Fork of ipxe; additional commands and features</subtitle>
<id>https://git.openslx.org/openslx-ng/ipxe.git/atom/src/usr?h=v0.9.5</id>
<link rel='self' href='https://git.openslx.org/openslx-ng/ipxe.git/atom/src/usr?h=v0.9.5'/>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/'/>
<updated>2008-07-31T15:55:46+00:00</updated>
<entry>
<title>[autoboot] Retain initial-slash (if present) when constructing TFTP URIs</title>
<updated>2008-07-31T15:55:46+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-07-31T15:55:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=481a21798daf0a805f048cabb65f3a80fc60fd06'/>
<id>urn:sha1:481a21798daf0a805f048cabb65f3a80fc60fd06</id>
<content type='text'>
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"  =&gt; URI="tftp://10.0.0.1/vmlinuz"
 cwuri="tftp://10.0.0.1/" filename="/vmlinuz" =&gt; 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"  =&gt; filename="vmlinuz"
  "kernel tftp://10.0.0.1//vmlinuz" =&gt; filename="/vmlinuz"
</content>
</entry>
<entry>
<title>[iSCSI] Support Windows Server 2008 direct iSCSI installation</title>
<updated>2008-07-17T16:45:17+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-07-17T16:45:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=03c80c12b8e9019554c3bd4545cf68926ee1ce47'/>
<id>urn:sha1:03c80c12b8e9019554c3bd4545cf68926ee1ce47</id>
<content type='text'>
Add yet another ugly hack to iscsiboot.c, this time to allow the user to
inhibit the shutdown/removal of the iSCSI INT13 device (and the network
devices, since they are required for the iSCSI device to function).

On the plus side, the fact that shutdown() now takes flags to
differentiate between shutdown-for-exit and shutdown-for-boot means that
another ugly hack (to allow returning via the PXE stack on BIOSes that
have broken INT 18 calls) will be easier.

I feel dirty.
</content>
</entry>
<entry>
<title>[image] Fail "imgexec"/"boot" if the image to execute is ambiguous</title>
<updated>2008-07-08T02:50:44+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-07-08T02:50:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=0436e417bcb9acd658b73a65172474a71eb12b83'/>
<id>urn:sha1:0436e417bcb9acd658b73a65172474a71eb12b83</id>
<content type='text'>
If there is more than one loaded image, refuse to automatically select
the image to execute.  There are at least two possible cases, with
different "correct" answers:

1. User loads image A by mistake, then loads image B and types "boot".
   User wants to execute image B.

2. User loads image A, then loads image B (which patches image A), then
   types "boot".  User wants to execute image A.

If a user actually wants to load multiple images, they must explicitly
specify which image is to be executed.
</content>
</entry>
<entry>
<title>[NETDEV] Add notion of link state</title>
<updated>2008-04-22T16:40:50+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-04-22T16:40:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=1ba959c6b342b314dfb01ca0a926ed6832c090b3'/>
<id>urn:sha1:1ba959c6b342b314dfb01ca0a926ed6832c090b3</id>
<content type='text'>
Add ability for network devices to flag link up/down state to the
networking core.

Autobooting code will now wait for link-up before attempting DHCP.

IPoIB reflects the Infiniband link state as the network device link state
(which is not strictly correct; we also need a succesful IPoIB IPv4
broadcast group join), but is probably more informative.
</content>
</entry>
<entry>
<title>[Settings] Remove assumption that all settings have DHCP tag values</title>
<updated>2008-03-25T20:46:16+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-03-25T20:46:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=92d15eff30410dcb0ec406e06b131fb7d9179ffd'/>
<id>urn:sha1:92d15eff30410dcb0ec406e06b131fb7d9179ffd</id>
<content type='text'>
Allow for settings to be described by something other than a DHCP option
tag if desirable.  Currently used only for the MAC address setting.

Separate out fake DHCP packet creation code from dhcp.c to fakedhcp.c.

Remove notion of settings from dhcppkt.c.

Rationalise dhcp.c to use settings API only for final registration of the
DHCP options, rather than using {store,fetch}_setting throughout.
</content>
</entry>
<entry>
<title>[DHCP] Fix up fake-packet creation as used by PXENV_GET_CACHED_INFO</title>
<updated>2008-03-23T21:58:05+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-03-23T21:58:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=ee4206a8a76c6d73c014f2261d4e7a1e093a40a8'/>
<id>urn:sha1:ee4206a8a76c6d73c014f2261d4e7a1e093a40a8</id>
<content type='text'>
Add dedicated functions create_dhcpdiscover(), create_dhcpack() and
create_proxydhcpack() for use by external code such as the PXE preboot
code.

Register ProxyDHCP options under the global scope "proxydhcp".

Unregister previously-acquired DHCP and ProxyDHCP settings when DHCP
succeeds.
</content>
</entry>
<entry>
<title>[Settings] Migrate DHCP and NVO code to the new settings API (untested)</title>
<updated>2008-03-21T22:15:31+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-03-21T22:15:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=8afb36c3bc08ff0c9bdf0a8496cb08a8bfe287f3'/>
<id>urn:sha1:8afb36c3bc08ff0c9bdf0a8496cb08a8bfe287f3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[Settings] Use a settings applicator to configure IPv4 routes.</title>
<updated>2008-03-21T00:01:27+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-03-21T00:01:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=aec9b8a41b6cad1b257c4e3a7f043f35871aafd0'/>
<id>urn:sha1:aec9b8a41b6cad1b257c4e3a7f043f35871aafd0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[Settings] Convert code in src/usr to use settings API.</title>
<updated>2008-03-20T23:42:11+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-03-20T23:42:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=eae6ac3d0bdb5f25193af9584db4eec9dd5226c9'/>
<id>urn:sha1:eae6ac3d0bdb5f25193af9584db4eec9dd5226c9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[Command] Add "sanboot" command.</title>
<updated>2008-03-04T17:59:26+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-03-04T17:59:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=b08a6f530042cfc0f8be2209cde9fab3d0ab9143'/>
<id>urn:sha1:b08a6f530042cfc0f8be2209cde9fab3d0ab9143</id>
<content type='text'>
</content>
</entry>
</feed>
