Configuration of a PXE Server
                                      
   for a stock 6.1 network booting installation
     _________________________________________________________________
   
Requirements for PXE Remote Installations:

    A. A DHCP Server within the subnet (not covered)
    B. A configured running PXE server within the subnet (covered)
    C. Network access to an installation tree (nfs, http or ftp) (not
       covered)
       
Six steps to getting a stock 6.1 installation to serve PXE.

    1. Install the pxe package
        ( bash# rpm -ivh /mnt/cdrom/RedHat/RPMS/pxe-0.1-9.i386.rpm )
    2. Copy the /misc/src/trees/boot/vmlinuz file from the installation
       tree to /tftpboot/X86PC/UNDI/linux-install/linux.1
        ( bash# cp /mnt/cdrom/misc/src/trees/boot/vmlinuz
            /tftpboot/X86PC/UNDI/linux-install/linux.1 )
    3. Copy the /misc/src/trees/initrd-network.img file from the
       installation tree to /tftpboot/X86PC/UNDI/linux-install/linux.2
        ( bash# cp /mnt/cdrom/misc/src/trees/initrd-network.img
            /tftpboot/X86PC/UNDI/linux-install/linux.2 )
    4. Edit the /etc/inetd.conf file and un-comment out this line:
        ( remove the # )
        #tftp dgram udp wait root /usr/sbin/tcpd in.tftpd
    5. Start the pxe service
        ( /etc/rc.d/init.d/pxe start )
    6. Restart the inetd service
        ( etc/rc.d/init.d/inetd restart )
       
   Upon completion of the above steps any PXE enabled machine within the
   subnet should boot from the network;
   
Booting/Installing from the Network

    1. Hardware Configuration
       Some hardware configuration will need to take place so that PXE
       booting is enabled on the machine. As this is very hardware
       specific this will not be covered here; please see the instruction
       manuals for the specific hardware.
    2. Booting
         i. DHCP
            Once the machine is booting with PXE you should see a message
            refering to one of the following: PXE, MBA and/or UNDI; after
            this screen you should see the machine attempting to get a
            responce from a DHCP server (note: that PXE will only accept
            DHCP from the PXE DHCP PROXY and not from dhcpd).
        ii. Boot Strap
            Upon acceptance of a DHCP address and recognition of the PXE
            server; the client will download the boot code and menu
            options from the server
        iii. Boot Selection
            When the boot strap is complete you will see this message:
             Press F8 to view menu ...
            Press F8 to see to boot selections. Select "Linux Remote
            Install". if you select "Local Boot", PXE will exit and allow
            the machine to continue booting as normal.
        iv. Network Loader
            The Linux Network Loader will offer to accept any extra
            kernel parmeters; once any options are entered the loader
            will download the kernel and the ramdisk image from the PXE
            server and the install will begin.
    3. Installation
       Once you've made it this far you're all set. Continue the install
       as normal; neither you nor the computer will know the difference!
       
Special Cases

    1. The DHCP Server is the same machine as the PXE server.
       In this case you will need to edit the /etc/pxe.conf file find
       this section:
        [UseDHCPPort]
            1
       Change the value to '0' to disable this action.
    2. You do not, or cannot, use MTFTP on your network.
       Edit the /etc/mtftpd.conf file and change
        [IsMulticastEnabled]
            1
       Change the value to '0'.
       
Trouble Shooting

   It has been noticed that some PXE aware NICs' may not properly
   allocate memory on non PXE aware motherboard. When this happens the
   ramdisk is not properly loaded. The currect work around is to pass the
   Network Boot Loader the memory kernel options. (ie mem=128M) The
   actual amount of ram is the suggested amount.