From 8f9f076c59b2652fdfc9fdfd24375ebb43bf5c1e Mon Sep 17 00:00:00 2001
From: Antony Messerli <antony@mes.ser.li>
Date: Sat, 9 Jan 2016 13:29:04 -0600
Subject: [PATCH] Adding docs for tftp booting and updating some others

---
 docs/boot_iso.md  |  9 ++++++++-
 docs/boot_tftp.md | 26 ++++++++++++++++++++++++++
 mkdocs.yml        |  1 +
 3 files changed, 35 insertions(+), 1 deletion(-)
 create mode 100644 docs/boot_tftp.md

diff --git a/docs/boot_iso.md b/docs/boot_iso.md
index 4d7358fb..2096e1b0 100644
--- a/docs/boot_iso.md
+++ b/docs/boot_iso.md
@@ -1,3 +1,10 @@
 ### Booting from ISO
 
-To create a bootable CD-ROM, burn the ISO image ipxe.iso (~1MB in size) to a blank CD-ROM.  You can also use this ISO file as a virtual CD device in Citrix XenServer, VMware ESXi, VMware Fusion, VirtualBox, or even in a Dell DRAC or HP iLOs virtual CD drive.
+#### Burning a CD/DVD
+To create a bootable CD-ROM/DVD, burn the ISO image [netboot.xyz-dhcp.iso](http://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.iso) if you have DHCP or [netboot.xyz-static.iso](http://boot.netboot.xyz/ipxe/netboot.xyz-static.iso) if you require manual entry (~1MB in size) to a blank CD-ROM/DVD.  Insert the media into the server, set the proper boot order and boot up.
+
+#### Virtual Machine Software
+You can also use these ISOs to boot any sort of VM in Citrix XenServer, VMware ESXi, VMware Fusion, VirtualBox. 
+
+#### Out of Band Virtual Media
+They are great for attaching to remote virtual media of a server like the Dell DRAC or HP iLOs.  Because the iPXE boot disk is so light weight, they are great for starting installations where there might be really low bandwidth.
diff --git a/docs/boot_tftp.md b/docs/boot_tftp.md
new file mode 100644
index 00000000..373cc6a1
--- /dev/null
+++ b/docs/boot_tftp.md
@@ -0,0 +1,26 @@
+### Booting from DHCP and TFTP
+
+If you want to utilize netboot.xyz from your home or office network, it's relatively easy to set up.  It will allow all of your devices on your network to have netboot.xyz available whenever you need it by just changing the boot order on your device, selecting network boot, or manually selecting the device to boot.
+
+#### DHCP Server Setup
+You will have to tell your DHCP server to provide a "next-server", the address of a TFTP server on your network, and a "filename", the [netboot.xyz DHCP boot file](http://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.kpxe).  When your clients boot up, if they are set to network boot, they'll automatically get a valid DHCP address, pull down the netboot.xyz iPXE bootloader and load up the Operating System menu.  
+
+Example:
+
+    next-server "1.2.3.4"
+    filename "netboot.xyz-dhcp.kpxe"
+
+#### TFTP Server Setup
+
+You will need to set up a tftp server to host the iPXE files.  There are various types of TFTP servers out there and they all usually work pretty well.  You can also use dnsmasq to host the files as well.
+
+If you use dnsmasq you can add this configuration to /etc/dnsmasq.conf:
+
+    enable-tftp
+    tftp-root=/var/lib/tftp
+    dhcp-boot=netboot.xyz-dhcp.kpxe
+
+#### Regular and Undionly Boot Files
+
+If you experiencing issues with the regular [netboot.xyz-dhcp.kpxe](http://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.kpxe) bootloader, you can try and use the [netboot.xyz-dhcp-undionly.kpxe](http://boot.netboot.xyz/ipxe/netboot.xyz-dhcp-undionly.kpxe) bootloader.  The regular bootloader includes common NIC drivers in the iPXE image, while the undionly loader will piggyback off the NIC boot firmware.
+ 
diff --git a/mkdocs.yml b/mkdocs.yml
index 81a08c8c..5337252a 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -10,6 +10,7 @@ pages:
 #    - 'Extlinux/Grub': 'boot_loaders.md'
     - 'iPXE': 'boot_ipxe.md'
     - 'ISO': 'boot_iso.md'
+    - 'TFTP': 'boot_tftp.md'
     - 'USB': 'boot_usb.md'
 #    - 'Virtual Box': 'boot_vbox.md'
 #    - 'VMware': 'boot_vmware.md'