<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openslx-ng/ipxe.git/src/include/gpxe/settings.h, branch v0.9.6</title>
<subtitle>Fork of ipxe; additional commands and features</subtitle>
<id>https://git.openslx.org/openslx-ng/ipxe.git/atom/src/include/gpxe/settings.h?h=v0.9.6</id>
<link rel='self' href='https://git.openslx.org/openslx-ng/ipxe.git/atom/src/include/gpxe/settings.h?h=v0.9.6'/>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/'/>
<updated>2008-10-30T21:47:14+00:00</updated>
<entry>
<title>[settings] Add the notion of a "tag magic" to numbered settings</title>
<updated>2008-10-30T21:47:14+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-10-29T18:17:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=0a6c66a83018c64d961ee4e8601ae8950cbee00b'/>
<id>urn:sha1:0a6c66a83018c64d961ee4e8601ae8950cbee00b</id>
<content type='text'>
Settings can be constructed using a dotted-decimal notation, to allow
for access to unnamed settings.  The default interpretation is as a
DHCP option number (with encapsulated options represented as
"&lt;encapsulating option&gt;.&lt;encapsulated option&gt;".

In several contexts (e.g. SMBIOS, Phantom CLP), it is useful to
interpret the dotted-decimal notation as referring to non-DHCP
options.  In this case, it becomes necessary for these contexts to
ignore standard DHCP options, otherwise we end up trying to, for
example, retrieve the boot filename from SMBIOS.

Allow settings blocks to specify a "tag magic".  When dotted-decimal
notation is used to construct a setting, the tag magic value of the
originating settings block will be ORed in to the tag number.
Store/fetch methods can then check for the magic number before
interpreting arbitrarily-numbered settings.
</content>
</entry>
<entry>
<title>[settings] Expose MAC address setting for general use</title>
<updated>2008-09-26T02:39:17+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-09-26T02:39:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=e2d5788716684889a4ea5548942e206414c06bbd'/>
<id>urn:sha1:e2d5788716684889a4ea5548942e206414c06bbd</id>
<content type='text'>
</content>
</entry>
<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>[Settings] Expose SMBIOS via settings API</title>
<updated>2008-03-28T15:35:06+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-03-28T15:35:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=feade5da6e0fd233b845d40c7a0a696ad1e35cc4'/>
<id>urn:sha1:feade5da6e0fd233b845d40c7a0a696ad1e35cc4</id>
<content type='text'>
In particular, expose the system UUID as a setting ("smbios/uuid").
</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>[Settings] copy_settings() should not fail if some settings are missing!</title>
<updated>2008-03-23T23:28:21+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-03-23T23:28:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=23e077666b5dd0bed8e7efec942c25faa242caf6'/>
<id>urn:sha1:23e077666b5dd0bed8e7efec942c25faa242caf6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[Settings] Implement simple_settings backed with extensible DHCP options</title>
<updated>2008-03-22T00:31:08+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-03-22T00:24:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=e5cea13e51f5226987048275499314c6f15d526f'/>
<id>urn:sha1:e5cea13e51f5226987048275499314c6f15d526f</id>
<content type='text'>
</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] 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>[Settings] Introduce settings applicators.</title>
<updated>2008-03-20T23:15:48+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2008-03-20T23:15:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=cf033046206aede5064c798bfa887fbb888b9217'/>
<id>urn:sha1:cf033046206aede5064c798bfa887fbb888b9217</id>
<content type='text'>
Convert DHCP option applicators in dns.c and iscsi.c to settings
applicators.

Kill off DHCP option applicators.
</content>
</entry>
</feed>
