<?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 appnotes</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-05-23T00:29:11-07:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/3c90x_issues?rev=1235941387&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/authmenus?rev=1362440099&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/autobootchainurl?rev=1257464785&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/bash_-_build_instructions?rev=1240496399&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/bootbymacaddress?rev=1265622464&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/compaq-armada-flashing?rev=1238320558&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/config?rev=1240527085&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/cow?rev=1235594642&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/dhcp_-_build_instructions?rev=1240516679&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/elf-ebi-initramfs-lnxi-howto?rev=1240542796&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/errors?rev=1240510250&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/fedora8iet?rev=1234923526&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/appnotes/gpxeonvmware?rev=1275641188&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/make_usb_drive?rev=1204171754&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/packages?rev=1240515606&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/port_winnt_sanboot?rev=1261524382&amp;do=diff"/>
                <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/san_transfer?rev=1260607631&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/sanboot-zfs?rev=1265921591&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/sed_-_build_instructions?rev=1240496182&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/srp_install?rev=1271797811&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/the_kernel?rev=1240535069&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/tinycore?rev=1237909232&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/varnishmirror?rev=1242917623&amp;do=diff"/>
                <rdf:li rdf:resource="http://etherboot.org/wiki/appnotes/winxp_smb?rev=1237323637&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/3c90x_issues?rev=1235941387&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-03-01T13:03:07-07:00</dc:date>
        <title>appnotes:3c90x_issues</title>
        <link>http://etherboot.org/wiki/appnotes/3c90x_issues?rev=1235941387&amp;do=diff</link>
        <description>2009-03-01 mdc
  Since the gPXE driver has been rewritten, this file is no longer
  accurate, but contains some potentially useful information that 
  should be cleaned up and integrated into the wiki.

	Instructions for use of the 3C90X driver for EtherBoot

		Original 3C905B support by:
			Greg Beeley (Greg.Beeley@LightSys.org),
			LightSys Technology Services, Inc.
			February 11, 1999

		Updates for 3C90X family by:
			Steve Smith (steve.smith@juno.com)
			October 1, 1999

		Minor documentat…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/authmenus?rev=1362440099&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-03-04T15:34:59-07:00</dc:date>
        <title>appnotes:authmenus</title>
        <link>http://etherboot.org/wiki/appnotes/authmenus?rev=1362440099&amp;do=diff</link>
        <description>User-specific boot menus

This page outlines the steps I took to implement a proof of concept comprising user authentication at preboot time and dynamically generated boot menus.  The user is first presented with a login screen.  The user's credentials are passed via an SSL-encrypted link to a server, which authenticates the user and then provides a boot menu containing a list of authorised boot selections.  The list of boot selections can vary according to the user.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/autobootchainurl?rev=1257464785&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-05T15:46:25-07:00</dc:date>
        <title>appnotes:autobootchainurl</title>
        <link>http://etherboot.org/wiki/appnotes/autobootchainurl?rev=1257464785&amp;do=diff</link>
        <description>Autoboot without a DHCP-supplied boot path

gPXE can be built with an embedded image, which might be a script. That script might look like this:


#!gpxe
dhcp net0
chain url://for.your/boot/script.gpxe


That is, obtain an IP address through DHCP on the first network interface and then load and run another script from a specific</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/bash_-_build_instructions?rev=1240496399&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-23T07:19:59-07:00</dc:date>
        <title>appnotes:bash_-_build_instructions</title>
        <link>http://etherboot.org/wiki/appnotes/bash_-_build_instructions?rev=1240496399&amp;do=diff</link>
        <description>Remember, as I stated earlier, we want to build everything as static binaries. This usually requires that we make some changes to the build process or invoke special switches for the config process.

Extract your BASH source archive in your /scratch directory. From /scratch execute “tar xvzf /scratch/bash-xxxxx.tar.gz” This assumes you have placed the archive in /scratch. If not, simply point to the correct location and extract the archive while in /scratch.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/bootbymacaddress?rev=1265622464&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-08T01:47:44-07:00</dc:date>
        <title>appnotes:bootbymacaddress</title>
        <link>http://etherboot.org/wiki/appnotes/bootbymacaddress?rev=1265622464&amp;do=diff</link>
        <description>Network booting by Mac Address

Author: Edward King




The environment

A collection of headless, diskless servers, utilising a range of operating system images.

A web-based control system enables a system administrator to pick from a range of operating system images for use by the specific machine, thereby adding it to the</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/compaq-armada-flashing?rev=1238320558&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-03-29T02:55:58-07:00</dc:date>
        <title>appnotes:compaq-armada-flashing</title>
        <link>http://etherboot.org/wiki/appnotes/compaq-armada-flashing?rev=1238320558&amp;do=diff</link>
        <description>Flashing gPXE ROM to a Compaq Armada Notebook

The Compaq Armada M700 (and also M300, V300, E500, E500S and Prosignia 170 and 190) has an build in PXE (Preboot eXecution Environment) Boot ROM for the internal Intel EtherExpress Pro 100 NIC (Network Interface Controller). This ROM is ok, if you only want to network boot from (the very stupid) TFTP Daemon. But what to do, if you want to netboot from i.e. HTTP or iSCSI? Yes right, you need gPXE.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/config?rev=1240527085&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-23T15:51:25-07:00</dc:date>
        <title>appnotes:config</title>
        <link>http://etherboot.org/wiki/appnotes/config?rev=1240527085&amp;do=diff</link>
        <description>#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.27.7
# Wed Apr 22 09:40:09 2009
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG=&quot;arch/x86/configs/i386_defconfig&quot;
# CONFIG_GENERIC_LOCKBREAK is not set
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_H…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/cow?rev=1235594642&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-02-25T12:44:02-07:00</dc:date>
        <title>appnotes:cow</title>
        <link>http://etherboot.org/wiki/appnotes/cow?rev=1235594642&amp;do=diff</link>
        <description>Copy on Write Vblade Server

If you want to support a lot of aoe clients, then using a copy on write device
may be the answer for you. I've written a small script that will setup
your loop device and device mapper configration for you. It will also run
vblade and link the approite cow block device with a aoe instance.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/dhcp_-_build_instructions?rev=1240516679&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-23T12:57:59-07:00</dc:date>
        <title>appnotes:dhcp_-_build_instructions</title>
        <link>http://etherboot.org/wiki/appnotes/dhcp_-_build_instructions?rev=1240516679&amp;do=diff</link>
        <description>Remember, as I stated earlier, we want to build everything as static binaries.  This usually requires that we make some changes to the build process or invoke special switches for the config process.



(Note : Due to compilation errors, you must download</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/elf-ebi-initramfs-lnxi-howto?rev=1240542796&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-23T20:13:16-07:00</dc:date>
        <title>appnotes:elf-ebi-initramfs-lnxi-howto</title>
        <link>http://etherboot.org/wiki/appnotes/elf-ebi-initramfs-lnxi-howto?rev=1240542796&amp;do=diff</link>
        <description>A howto guide to building the kernel initramfs and bundling those into one .ebi or .elf file using wraplinux.
This document is and will be for some time, a work in progress.  I plan to include any scripts and related items that are generated, and to explain things as best I can.  Over time, I hope this document reaches an point of simplicity that can only be duplicated, not surpassed.  This document is focused around 2.6 Kernels, although it would probably work on 2.4 kernels, I do not have the …</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/errors?rev=1240510250&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-23T11:10:50-07:00</dc:date>
        <title>appnotes:errors</title>
        <link>http://etherboot.org/wiki/appnotes/errors?rev=1240510250&amp;do=diff</link>
        <description>I did some google searches and found what appeared to be a pretty promising fix here.&lt;http://bugs.gentoo.org/229183&gt;</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/fedora8iet?rev=1234923526&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-02-17T18:18:46-07:00</dc:date>
        <title>appnotes:fedora8iet</title>
        <link>http://etherboot.org/wiki/appnotes/fedora8iet?rev=1234923526&amp;do=diff</link>
        <description>Installing the iSCSI Enterprise Target on Fedora 8

Background

The words target and initiator have special meanings in the storage world. An initiator requests disk services from a target. You can generally think of the the disk drive itself as the target and the storage controller as the initiator. Initiators initiate transactions with targets.</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/appnotes/gpxeonvmware?rev=1275641188&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-06-04T01:46:28-07:00</dc:date>
        <title>appnotes:gpxeonvmware</title>
        <link>http://etherboot.org/wiki/appnotes/gpxeonvmware?rev=1275641188&amp;do=diff</link>
        <description>Adding a gPXE ROM image directly into a VMware virtual machine

	*  This guide covers VMWare virtual machines and should be nearly identical for all VMware hypervisor prodcuts.  VMWare Workstation is covered specifically by this guide, but you can adapt it easily for VMWare Server or ESX.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/make_usb_drive?rev=1204171754&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-27T20:09:14-07:00</dc:date>
        <title>appnotes:make_usb_drive</title>
        <link>http://etherboot.org/wiki/appnotes/make_usb_drive?rev=1204171754&amp;do=diff</link>
        <description>Making a bootable USB flash drive

How to upgrade your motherboard BIOS firmware from a USB thumb drive
How to make a USB memory key in to a bootable DOS drive
By: Jeff Campbell, Turks &amp; Caicos Islands, British West Indies
June 25, 2007

It happens all the time, you have a newish machine that lacks a floppy drive, and you have a need to either upgrade the BIOS from DOS or run some other esoteric application that can only be done from DOS – the problem is, with no floppy drive (and god only knows…</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/packages?rev=1240515606&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-23T12:40:06-07:00</dc:date>
        <title>appnotes:packages</title>
        <link>http://etherboot.org/wiki/appnotes/packages?rev=1240515606&amp;do=diff</link>
        <description>When ever possible, a package should be built to STATIC binary specifications, NOT dynamic.

&lt;http://ftp.isc.org/isc/dhcp/&gt; - DHCP - Build instructions

&lt;ftp://ftp.gnu.org/gnu/sed/&gt;   - SED  - Build instructions

&lt;http://ftp.gnu.org/gnu/bash/&gt; - BASH - Build instructions</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/port_winnt_sanboot?rev=1261524382&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-12-22T15:26:22-07:00</dc:date>
        <title>appnotes:port_winnt_sanboot</title>
        <link>http://etherboot.org/wiki/appnotes/port_winnt_sanboot?rev=1261524382&amp;do=diff</link>
        <description>Porting Windows XP, Windows 7 and Windows 2008 to New Target Hardware via SAN-Booting

Introduction

Experience the power of Free and Open-Source Software such as gPXE and the communities that develop and support such.  If you can appreciate what this article accomplishes, perhaps you'd be inclined to get in the</description>
    </item>
    <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/san_transfer?rev=1260607631&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-12-12T00:47:11-07:00</dc:date>
        <title>appnotes:san_transfer</title>
        <link>http://etherboot.org/wiki/appnotes/san_transfer?rev=1260607631&amp;do=diff</link>
        <description>SAN image transfer

This page documents various techniques that people have found useful for transferring disk images to a SAN target.

netcat

If the source machine does only have one HDD which has been used completely, netcat can be used to transfer the image to the target in one step:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/sanboot-zfs?rev=1265921591&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-11T12:53:11-07:00</dc:date>
        <title>appnotes:sanboot-zfs</title>
        <link>http://etherboot.org/wiki/appnotes/sanboot-zfs?rev=1265921591&amp;do=diff</link>
        <description>The volume management functions of ZFS, combined with the COMSTAR (STMF) system in Opensolaris create a very powerful storage platform for boot-from-SAN functionality.  This document endeavors to describe that configuration.

Components

The following are the major components of this system:</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/sed_-_build_instructions?rev=1240496182&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-23T07:16:22-07:00</dc:date>
        <title>appnotes:sed_-_build_instructions</title>
        <link>http://etherboot.org/wiki/appnotes/sed_-_build_instructions?rev=1240496182&amp;do=diff</link>
        <description>Remember, as I stated earlier, we want to build everything as static binaries. This usually requires that we make some changes to the build process or invoke special switches for the config process.

Extract your SED source archive in your /scratch directory. From /scratch execute “tar xvzf /scratch/sed-xxx.xx.tar.gz” This assumes you have placed the archive in /scratch. If not, simply point to the correct location and extract the archive while in /scratch.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/srp_install?rev=1271797811&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-04-20T14:10:11-07:00</dc:date>
        <title>appnotes:srp_install</title>
        <link>http://etherboot.org/wiki/appnotes/srp_install?rev=1271797811&amp;do=diff</link>
        <description>SCSI RDMA Protocol (SRP) improves the read performance in terms of throughput which is increased significantly for both random read with good locality and sequential read.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/the_kernel?rev=1240535069&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-23T18:04:29-07:00</dc:date>
        <title>appnotes:the_kernel</title>
        <link>http://etherboot.org/wiki/appnotes/the_kernel?rev=1240535069&amp;do=diff</link>
        <description>The kernel I am focused on in this Wiki is 2.6.27.7. 

In regard to network booting, any 2.6 kernel should technically work.  Some where in the build chain of the 2.6 kernel there were some format changes. 

If you go low enough in the 2.6 build chain, you may experience some problems.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/tinycore?rev=1237909232&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-03-24T08:40:32-07:00</dc:date>
        <title>appnotes:tinycore</title>
        <link>http://etherboot.org/wiki/appnotes/tinycore?rev=1237909232&amp;do=diff</link>
        <description>Tiny Core Linux over HTTP

This application note describes how Tiny Core Linux can be HTTP-booted using the gPXE network bootloader.

Overview

Although Tiny Core Linux comes with PXE netboot support, HTTP booting is attractive because it is more flexible.  Only a HTTP server is required (rather than a full DHCP + TFTP setup).  HTTP also works well over the internet.</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/varnishmirror?rev=1242917623&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-05-21T07:53:43-07:00</dc:date>
        <title>appnotes:varnishmirror</title>
        <link>http://etherboot.org/wiki/appnotes/varnishmirror?rev=1242917623&amp;do=diff</link>
        <description>Introduction

By using a reverse proxy, it is possible to create an HTTP mirror without of the heavy burden of rsync and a large amount of allocated space.  The reverse proxy will cache the particular files (with special cases to exclude repository files)</description>
    </item>
    <item rdf:about="http://etherboot.org/wiki/appnotes/winxp_smb?rev=1237323637&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-03-17T14:00:37-07:00</dc:date>
        <title>appnotes:winxp_smb</title>
        <link>http://etherboot.org/wiki/appnotes/winxp_smb?rev=1237323637&amp;do=diff</link>
        <description>Booting Windows XP SP2 over SMB

Windows XP SP2 Professional's RIS support allows for it to boot entirely over SMB.  (Technically, the initial boot files are transferred over TFTP.)

Setup the Share

Create a directory on your hosting Windows system called</description>
    </item>
</rdf:RDF>
