<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openslx-ng/ipxe.git/src/core, branch v1.0.0</title>
<subtitle>Fork of ipxe; additional commands and features</subtitle>
<id>https://git.openslx.org/openslx-ng/ipxe.git/atom/src/core?h=v1.0.0</id>
<link rel='self' href='https://git.openslx.org/openslx-ng/ipxe.git/atom/src/core?h=v1.0.0'/>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/'/>
<updated>2010-02-01T00:22:43+00:00</updated>
<entry>
<title>[proto] Remove unsupported IGMP protocol</title>
<updated>2010-02-01T00:22:43+00:00</updated>
<author>
<name>Stefan Hajnoczi</name>
</author>
<published>2010-01-30T09:55:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=00a780e38fd5878d3e1f6f19830b2a0abf3cdf95'/>
<id>urn:sha1:00a780e38fd5878d3e1f6f19830b2a0abf3cdf95</id>
<content type='text'>
The IGMP code came from legacy Etherboot and was never updated to work
as a gPXE protocol.  There has been no demand for this protocol, so this
patch removes it.

Signed-off-by: Stefan Hajnoczi &lt;stefanha@gmail.com&gt;
Signed-off-by: Marty Connor &lt;mdc@etherboot.org&gt;
</content>
</entry>
<entry>
<title>[proto] Remove unsupported NFS protocol</title>
<updated>2010-02-01T00:21:00+00:00</updated>
<author>
<name>Stefan Hajnoczi</name>
</author>
<published>2010-01-30T09:48:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=1548189ffa8a54275ed58476993dba6dcaf799a0'/>
<id>urn:sha1:1548189ffa8a54275ed58476993dba6dcaf799a0</id>
<content type='text'>
The NFS protocol code came from legacy Etherboot and was never updated
to work as a gPXE protocol.  There has been no demand for this protocol,
so this patch removes it.

I have an unfinished NFSv3 over TCP implementation for gPXE that can be
used as the base for new work, should we want to resurrect this
protocol.

Signed-off-by: Stefan Hajnoczi &lt;stefanha@gmail.com&gt;
Signed-off-by: Marty Connor &lt;mdc@etherboot.org&gt;
</content>
</entry>
<entry>
<title>[uri] Handle an empty unparse_uri() result properly</title>
<updated>2010-01-27T13:50:49+00:00</updated>
<author>
<name>Joshua Oreman</name>
</author>
<published>2010-01-27T04:55:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=e6f08b0aa79a07bcadff203c91245db0dcd155b7'/>
<id>urn:sha1:e6f08b0aa79a07bcadff203c91245db0dcd155b7</id>
<content type='text'>
Previously, if none of the URI parts requested existed in the passed
URI, unparse_uri() would not touch the destination buffer at all; this
could lead to use of uninitialized data. Fix by setting buf[0] = '\0'
before unparsing whenever we have room to do so.

Signed-off-by: Joshua Oreman &lt;oremanj@rwcr.net&gt;
Signed-off-by: Marty Connor &lt;mdc@etherboot.org&gt;
</content>
</entry>
<entry>
<title>[uri] Decode/encode URIs when parsing/unparsing</title>
<updated>2010-01-20T23:14:28+00:00</updated>
<author>
<name>Joshua Oreman</name>
</author>
<published>2009-12-30T03:36:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=3d9dd93a1452e28c728483b03e352691238491ed'/>
<id>urn:sha1:3d9dd93a1452e28c728483b03e352691238491ed</id>
<content type='text'>
Currently, handling of URI escapes is ad-hoc; escaped strings are
stored as-is in the URI structure, and it is up to the individual
protocol to unescape as necessary. This is error-prone and expensive
in terms of code size. Modify this behavior by unescaping in
parse_uri() and escaping in unparse_uri() those fields that typically
handle URI escapes (hostname, user, password, path, query, fragment),
and allowing unparse_uri() to accept a subset of fields to print so
it can be easily used to generate e.g. the escaped HTTP path?query
request.

Signed-off-by: Joshua Oreman &lt;oremanj@rwcr.net&gt;
Signed-off-by: Marty Connor &lt;mdc@etherboot.org&gt;
</content>
</entry>
<entry>
<title>[settings] Add automagic "netX" settings block for last opened netdev</title>
<updated>2010-01-20T22:52:02+00:00</updated>
<author>
<name>Joshua Oreman</name>
</author>
<published>2009-10-22T04:55:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=ef9d1a32c6dc83d1086141c18d2be19a05ab8e49'/>
<id>urn:sha1:ef9d1a32c6dc83d1086141c18d2be19a05ab8e49</id>
<content type='text'>
A script loaded via autoboot may want to get some of the settings (MAC
address, IP address, et cetera) for the interface via which it was
loaded, in order to pass them to the operating system. Previously such
a script had no way to determine what to put in the X of ${netX/foo}.

Solve this problem by transparently forwarding accesses to the real
settings associated with the most recently opened network device,
so scripts in this situation can say literally ${netX/foo} and get
the foo setting they want.

Signed-off-by: Marty Connor &lt;mdc@etherboot.org&gt;
</content>
</entry>
<entry>
<title>[uri] Fix outdated comment in parse_uri()</title>
<updated>2009-11-21T01:42:03+00:00</updated>
<author>
<name>sobtwmxt</name>
</author>
<published>2009-11-19T11:25:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=71e77b8cc20b8fd22e83568837a5eda7d9d02bb0'/>
<id>urn:sha1:71e77b8cc20b8fd22e83568837a5eda7d9d02bb0</id>
<content type='text'>
Signed-off-by: Marty Connor &lt;mdc@etherboot.org&gt;
</content>
</entry>
<entry>
<title>[linker] Add mechanism for subsystem-dependent configuration options</title>
<updated>2009-11-21T01:30:58+00:00</updated>
<author>
<name>Joshua Oreman</name>
</author>
<published>2009-08-07T01:52:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=9a0bd0711f9e5d0a555fa35de8eb07cb29dc83a9'/>
<id>urn:sha1:9a0bd0711f9e5d0a555fa35de8eb07cb29dc83a9</id>
<content type='text'>
It is often the case that some module of gPXE is only relevant if the
subsystem it depends on is already being included. For instance,
commands to manage wireless interfaces are quite useless if no
compiled-in driver has pulled in the wireless networking stack. There
may be a user-modifiable configuration options for these dependent
modules, but even if enabled, they should not be included when they
would be useless.

Solve this by allowing the creation of config_subsystem.c, for
configuration directives like those in the global config.c that should
only be considered when subsystem.c is included in the final gPXE
build.

For consistency, move core/config.c to the config/ directory, where
the other config_subsystem.c files will eventually reside.

Signed-off-by: Marty Connor &lt;mdc@etherboot.org&gt;
</content>
</entry>
<entry>
<title>[job] Report progress of downloader jobs via job_progress()</title>
<updated>2009-08-31T18:33:55+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-08-31T18:33:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=c9c411286aebc4c46539fad2c80a950ab80e68e8'/>
<id>urn:sha1:c9c411286aebc4c46539fad2c80a950ab80e68e8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[job] Add missing job_progress() interface method</title>
<updated>2009-08-31T18:33:05+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-08-31T18:33:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=0fc13add3196216cb440fbcee136903263a82f3f'/>
<id>urn:sha1:0fc13add3196216cb440fbcee136903263a82f3f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[infiniband] Add support for SRP over Infiniband</title>
<updated>2009-08-10T21:27:33+00:00</updated>
<author>
<name>Michael Brown</name>
</author>
<published>2009-07-17T21:11:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.openslx.org/openslx-ng/ipxe.git/commit/?id=0c30dc6bc5f26e7011ddfcda34d7adac653464cf'/>
<id>urn:sha1:0c30dc6bc5f26e7011ddfcda34d7adac653464cf</id>
<content type='text'>
SRP is the SCSI RDMA Protocol.  It allows for a method of SAN booting
whereby the target is responsible for reading and writing data using
Remote DMA directly to the initiator's memory.  The software initiator
merely sends and receives SCSI commands; it never has to touch the
actual data.
</content>
</entry>
</feed>
