<?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</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-10-11T23:19:40-07:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/pxelinux_tftp_to_http_migration?rev=1289128700&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/gpxeonqemu091?rev=1271142592&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/soc/2011/meteger/journal/week12?rev=1313334396&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/appnotes/pxelinux_tftp_to_http_migration?rev=1289128700&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-11-07T03:18:20-07:00</dc:date>
        <title>appnotes:pxelinux_tftp_to_http_migration</title>
        <link>http://etherboot.org/wiki/appnotes/pxelinux_tftp_to_http_migration?rev=1289128700&amp;do=diff</link>
        <description>PXELINUX TFTP to HTTP Migration

The Problem

Migrate from PXELINUX/TFTP deployment environment to gPXE/HTTP based environment with easy roll out and back out, and zero changes to PXELINUX menu/configuration files and production application code that drives deployment operations. Eventually replace</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/gpxeonqemu091?rev=1271142592&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-04-13T00:09:52-07:00</dc:date>
        <title>appnotes:gpxeonqemu091</title>
        <link>http://etherboot.org/wiki/appnotes/gpxeonqemu091?rev=1271142592&amp;do=diff</link>
        <description>How to use gPXE with RHEL 5.4 (qemu-kvm 0.9.1)

Introduction

QEMU/KVM in RedHat Enterprise Linux 5.4 uses a version based on qemu
0.9.1 with kvm-83.
The etherboot roms are included by default in that package.

In order to use the gPXE some patches may be applied to the qemu
source as well as to gPXE source.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/soc/2011/meteger/journal/week12?rev=1313334396&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-14T08:06:36-07:00</dc:date>
        <title>soc:2011:meteger:journal:week12</title>
        <link>http://etherboot.org/wiki/soc/2011/meteger/journal/week12?rev=1313334396&amp;do=diff</link>
        <description>Day 1 ( Aug 8 )

I did some cleanups in the code today. I also implemented tg3_close() and tg3_remove_one(). Those were the last two missing functions and implementing them resulted in a successful first boot of the driver :).

Day 2 ( Aug 9 )

More cleanups. Removed most of the out-commented code that was left in the driver and some other simplifications. While going through the code I also compiled a list of suspicious looking things that I want to revisit the coming days.</description>
    </item>
</rdf:RDF>
