<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://etherboot.org/wiki/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://etherboot.org/wiki/feed.php">
        <title>Etherboot/gPXE Wiki soc:2006:alanshieh</title>
        <description></description>
        <link>http://etherboot.org/wiki/</link>
        <image rdf:resource="http://etherboot.org/wiki/lib/tpl/monobook/images/favicon.ico" />
       <dc:date>2026-04-20T13:01:24-07:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2006/alanshieh/oldundiproposal?rev=1210407926&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2006/alanshieh/start?rev=1210407891&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://etherboot.org/wiki/lib/tpl/monobook/images/favicon.ico">
        <title>Etherboot/gPXE Wiki</title>
        <link>http://etherboot.org/wiki/</link>
        <url>http://etherboot.org/wiki/lib/tpl/monobook/images/favicon.ico</url>
    </image>
    <item rdf:about="http://etherboot.org/wiki/soc/2006/alanshieh/oldundiproposal?rev=1210407926&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-05-10T01:25:26-07:00</dc:date>
        <title>soc:2006:alanshieh:oldundiproposal</title>
        <link>http://etherboot.org/wiki/soc/2006/alanshieh/oldundiproposal?rev=1210407926&amp;do=diff</link>
        <description>= Deliverables and expected timeline =

The initial target platform will be VMware, which provides e1000 and
vlance emulated NICs, which support PXE.

The architecture for the UNDI driver will be divided into two
portions: a userspace program for executing the UNDI code, which
passes packets to and from an in-kernel component.

Based on my understanding of the Etherboot code and (non-functional)
Grub UNDI driver, UNDI is typically implemented as real-mode code. The
natural way to execute the rea…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2006/alanshieh/start?rev=1210407891&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-05-10T01:24:51-07:00</dc:date>
        <title>soc:2006:alanshieh:start</title>
        <link>http://etherboot.org/wiki/soc/2006/alanshieh/start?rev=1210407891&amp;do=diff</link>
        <description>Alan Shieh, Linux UNDI Driver

Comparing a UNDI driver to server-side initrd selection

It is possible to achieve the same effect as an UNDI driver with other approaches, such as loading all possible drivers into an initrd, or selecting an initrd based on MAC address, thus allowing Linux to load the right module. Such a design of this is much more conservative, as it relies on driver code that has been used by a larger population</description>
    </item>
</rdf:RDF>
