Removes docs from netboot.xyz repo

As the main site no longer uses mkdocs, this removes
older documentation and transitions to using the
hugo repo for docs.

README.md

@@ -32,8 +32,15 @@ If you already have iPXE up and running on the network, you can hit netboot.xyz
 
 You'll need to make sure to have [DOWNLOAD_PROTO_HTTPS](https://github.com/ipxe/ipxe/blob/master/src/config/general.h#L56) enabled in iPXE.
 
-Full documentation is at netboot.xyz:
-* [https://netboot.xyz](https://netboot.xyz)
+### Documentation
+
+See [netboot.xyz](https://netboot.xyz) for all documentation.  Some links to get started with are:
+
+* [Downloads](https://netboot.xyz/downloads/)
+* [Booting Methods](https://netboot.xyz/booting/)
+* [FAQ](https://netboot.xyz/faq/)
+
+If you'd like to contribute to the documentation, the netboot.xyz documenation is located at [netboot.xyz-docs](https://github.com/antonym/netboot.xyz-docs).
 
 ### What Operating Systems are available?
 
@@ -79,10 +86,10 @@ Full documentation is at netboot.xyz:
 * [SystemRescueCD](https://www.system-rescue-cd.org)
 * [Ultimate Boot CD](http://www.ultimatebootcd.com)
 
-#### Testing New Branches
+### Testing New Branches
 
 Under the **Utilities** menu on netboot.xyz, there's an option for ["Test netboot.xyz branch"](https://github.com/antonym/netboot.xyz/blob/master/src/utils.ipxe#L157).  If you've forked the code and have developed a new feature branch, you can use this option to chainload into that branch to test and validate the code.  All you need to do is specify your Github user name and the name of your branch or abbreviated hash of the commit. Also, disable the signature verification for *netboot.xyz* under **Signatures Checks**.
 
-#### Feedback
+### Feedback
 
 Feel free to open up an [issue](https://github.com/antonym/netboot.xyz/issues) on Github, swing by [Freenode IRC](http://freenode.net/) in the [#netbootxyz](http://webchat.freenode.net/?channels=#netbootxyz) channel, or ping us on [Discord](https://discord.gg/An6PA2a).  Follow us on [Twitter](https://twitter.com/netbootxyz) or like us on [Facebook](https://www.facebook.com/netboot.xyz)!

docs/CNAME

@@ -1 +0,0 @@
-netboot.xyz

docs/boot-drac.md

@@ -1,2 +0,0 @@
-# Dell DRAC
-TBA

docs/boot-ilo.md

@@ -1,2 +0,0 @@
-# HP iLO
-TBA

docs/boot-ipxe.md

@@ -1,17 +0,0 @@
-# iPXE
-
-### NIC with Embedded iPXE
-
-If you've already compiled your own iPXE, you can load up the netboot.xyz menu easily by entering CTRL-B when prompted setting DHCP and then chainloading iPXE:
-
-    dhcp
-    chain --autofree https://boot.netboot.xyz
-
-If you don't have DHCP on your network, you can manually set your network information:
-
-    set net0/ip <ip>
-    set net0/netmask <netmask>
-    set net0/gateway <gateway>
-    set dns <nameserver>
-    ifopen net0
-    chain --autofree https://boot.netboot.xyz

docs/boot-iso.md

@@ -1,10 +0,0 @@
-# Booting from ISO
-
-### Burning a CD/DVD
-To create a bootable CD-ROM/DVD, burn the ISO image [netboot.xyz.iso](https://boot.netboot.xyz/ipxe/netboot.xyz.iso) 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.

docs/boot-loaders.md

@@ -1,17 +0,0 @@
-# Boot as iPXE Linux Kernel
-
-The ipxe.lkrn file can be booted as a Linux kernel from the bootloader.  This can be useful for providing a diagnostic tool as part of the OS or even having a quick option to reprovision the server on the fly.
-
-### Extlinux
-
-Edit /boot/extlinux.conf and add a simple entry:
-
-    LABEL ipxe-boot
-          kernel /boot/ipxe.lkrn
-          initrd /boot/ipxe-config.ipxe
-
-The kernel is treated as a Linux kernel and the initrd is treated as the iPXE script that is run once the kernel has loaded.
-
-### Grub
-
-

docs/boot-tftp.md

@@ -1,26 +0,0 @@
-# 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 boot file](https://boot.netboot.xyz/ipxe/netboot.xyz.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.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.kpxe
-
-### Regular and Undionly Boot Files
-
-If you experiencing issues with the regular [netboot.xyz.kpxe](https://boot.netboot.xyz/ipxe/netboot.xyz.kpxe) bootloader, you can try and use the [netboot.xyz-undionly.kpxe](https://boot.netboot.xyz/ipxe/netboot.xyz-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.
- 

docs/boot-usb.md

@@ -1,69 +0,0 @@
-# Booting from a USB Key
-
-*Warning: Backup your important data before using USB as it will overwrite anything on the USB key.*
-
-Download a netboot.xyz USB disk:
-
-* [netboot.xyz](https://boot.netboot.xyz/ipxe/netboot.xyz.usb) 
-
-## GUI Tool (Windows/Linux/macOS)
-
-If you prefer a graphical tool to write the image to USB, check out [Etcher](https://balena.io/etcher) as a simple and easy to use tool for Linux/Mac/Windows. You download the correct version for your operating system, extract and/or run it, then select the image you want to write, and the target USB/SD card you want to write it to. If it doesn't recognize the image's extension but you know it is a bootable USB/SD image, you can change the extension to .bin or .img to allow Etcher to "see" it and write it to your drive.
-
-## Creating USB Key on Linux
-
-Insert a USB key in your compute and find the device name. Then use following command:
-
-    cat ipxe.usb > /dev/sdX
-
-or
-
-    dd if=ipxe.usb of=/dev/sdX
-
-where sdX is your usb drive.
-
-The USB key should be ready to eject once finished.
-
-### Creating USB Key on MacOS
-
-__Run:__
-
-    diskutil list
-
-to get the current list of devices
-
-___Insert the flash media.___
-
-__Run:__
-
-    diskutil list
-
-again and determine the device node assigned to your flash media (e.g. /dev/disk2).
-
-__Run:__
-
-    diskutil unmountDisk /dev/diskN
-
-(replace N with the disk number from the last command; in the previous example, N would be 2).
-
-__Execute:__
-
-    sudo dd if=netboot.xyz.usb of=/dev/rdiskN bs=1m
-
-* Using /dev/rdisk instead of /dev/disk may be faster
-* If you see the error dd: Invalid number '1m', you are using GNU dd. Use the same command but replace bs=1m with bs=1M
-* If you see the error dd: /dev/diskN: Resource busy, make sure the disk is not in use. Start the 'Disk Utility.app' and unmount (don't eject) the drive
-
-__Run:__
-
-    diskutil eject /dev/diskN
-
-and remove your flash media when the command completes.
-
-### Creating USB Key on Windows
-
-Check out [Rufus](https://rufus.akeo.ie/) to install the ISO file to a USB key.
-
-### Booting
-
-Once you've created your key, reboot and set your BIOS to load the USB key first if it's not set for that already. You should see iPXE load up either load up netboot.xyz automatically or prompt you to set your networking information up.

docs/boot-vbox.md

@@ -1,2 +0,0 @@
-# VirtualBox
-TBA

docs/boot-vmware.md

@@ -1,24 +0,0 @@
-# Boot from VMware 
-
-### VMware Fusion
-
-These instructions are for setting up netboot.xyz in a VM on VMware's Fusion for MacOS.
-
-### Create the VM
-
-* Add a new virtual machine.
-* Select "Install from disc or image".
-* Click on "Use another disk or disc image...".
-* Download and select the netboot.xyz [ISO](https://boot.netboot.xyz/ipxe/netboot.xyz.iso).
-* On the Choose Operating System Screen, select the OS type you are planning on installing.  If you plan on testing multiple types of installs, you can just choose a CentOS 64-bit OS.
-* Click the "Customize Settings" and give the VM a name, like "netboot.xyz".
-
-This will create your VM.  
-
-### Running the VM
-
-_You'll need to adjust the memory settings of the VM to ensure you'll have enough memory to run the OS installers in memory.  Typically it's good to bump the memory up to 2GB to 4GB._
-
-* Click the wrench icon and click on Processors & Memory and bump up the memory to the desired amount of memory.
-* Start the VM up and you should see the netboot.xyz loader.
-* If you determine you no longer want to boot from netboot.xyz, you can either change the boot order to boot from the hard drive by default or delete the ISO from the VM.

docs/contributing.md

@@ -1 +0,0 @@
-../CONTRIBUTING.md

docs/faq.md

@@ -1,33 +0,0 @@
-# Frequently Asked Questions
-
-## What is this?
-netboot.xyz is tool that allows you to boot your favorite Operating System's installer or various utilities over the network with minimal overhead and all from a single menu system.  It's similar to various tools netbooting tools of the past like boot.kernel.org with a lot more flexibility.  The boot loader is very light weight being under 1MB in size which translates into a very quick time to create a USB key.
-
-## How does this work?
-netboot.xyz uses an open source tool called iPXE.  The bootloader used calls to a webserver that hosts that the iPXE source files.  The iPXE source files contain menus and logic that understand how the various Linux installers operate.  When you select an Operating System, netboot.xyz retrieves the images from the project directory when possible or known and trusted performant mirrors.  The location the file is pulled from is always displayed during retrieval.
-
-## Will my favorite distribution work?
-Usually you need three things to boot up an OS, the vmlinuz, the initramfs, and the rootfs.  Distributions that support an installer kernel hosted on a mirror are typically the easier ones to implement.  Distributions that only release as ISOs typically are harder to implement as we have to use memdisk to load it up into memory.  
-
-From [syslinux - memdisk](http://www.syslinux.org/wiki/index.php/MEMDISK): The majority of Linux based CD images will also fail to work with MEMDISK ISO emulation. Linux distributions require kernel and initrd files to be specified, as soon as these files are loaded the protected mode kernel driver(s) take control and the virtual CD will no longer be accessible. If any other files are required from the CD/DVD they will be missing, resulting in boot error(s). Linux distributions that only require kernel and initrd files function fully via ISO emulation, as no other data needs accessing from the virtual CD/DVD drive once they have been loaded. The boot loader has read all necessary files to memory by using INT 13h, before booting the kernel.
-
-You can read more about my thoughts and possible solutions [here](https://www.reversengineered.com/2016/01/07/booting-linux-isos-with-memdisk-and-ipxe/).
-
-## My distribution uses ISOs for delivery, how can I see if they work?
-You can do a quick check by loading up netboot.xyz in a virtual environment baremetal.  Make sure you have plenty of RAM as you are loading the ISO into RAM.  Then select the iPXE command line and enter the following;
-
-    kernel https://boot.netboot.xyz/memdisk iso raw
-    initrd http://url/to/iso
-    boot
-
-That should load the ISO and if you make it all the way into the installer, great, your OS may work.  If it fails during initramfs load trying to load the CD device, then it has the issue of not being able to find the ISO in memory.
-
-## Can I create my own configurations?
-
-Yes!  You can fork [netboot.xyz-custom](https://github.com/antonym/netboot.xyz-custom) and create your own menu.  You can then set your Github user from the Utility menu and your menu will show up in the main menu.  If you don't want to set your user every time, you can custom compile the netboot.xyz iPXE code and include your github_user during the compile.  This allows you to create your own menu without the maintenance of everything else.
-
-## What are some good resources for learning more about network booting?
-
-* [The iPXE Project](http://ipxe.org/)
-* [NetworkBoot.org](http://networkboot.org/)
-* [Syslinux Project](http://www.syslinux.org/wiki/index.php?title=The_Syslinux_Project)

docs/index.md

@@ -1,102 +0,0 @@
-# netboot.xyz 
-
-[![Build Status](https://travis-ci.org/antonym/netboot.xyz.svg?branch=master)](https://travis-ci.org/antonym/netboot.xyz)
-[![Discord](https://img.shields.io/discord/425186187368595466)](https://discord.gg/An6PA2a)
-
-![netboot.xyz menu](img/netboot.xyz.gif)
-
-### Bootloader Downloads
-
-These iPXE disks will automatically load into [boot.netboot.xyz](https://boot.netboot.xyz):
-
-| Type | Bootloader | Description |
-|------|------------|-------------|
-|ISO (Legacy)| [netboot.xyz.iso](https://boot.netboot.xyz/ipxe/netboot.xyz.iso)| Used for CD/DVD, Virtual CDs like DRAC/iLO, VMware, Virtual Box (Legacy) |
-|ISO (EFI)|[netboot.xyz-efi.iso](https://boot.netboot.xyz/ipxe/netboot.xyz-efi.iso)| Same as ISO (Legacy) but used for EFI BIOS, works in Virtual Box EFI mode |
-|Floppy| [netboot.xyz.dsk](https://boot.netboot.xyz/ipxe/netboot.xyz.dsk)| Used for 1.44 MB floppies, Virtual floppies like DRAC/iLO, VMware, Virtual Box|
-|USB| [netboot.xyz.usb](https://boot.netboot.xyz/ipxe/netboot.xyz.usb)| Used for creation of USB Keys|
-|Kernel| [netboot.xyz.lkrn](https://boot.netboot.xyz/ipxe/netboot.xyz.lkrn)| Used for booting from GRUB/EXTLINUX|
-|DHCP| [netboot.xyz.kpxe](https://boot.netboot.xyz/ipxe/netboot.xyz.kpxe)| DHCP boot image file, uses built-in iPXE NIC drivers|
-|DHCP-undionly| [netboot.xyz-undionly.kpxe](https://boot.netboot.xyz/ipxe/netboot.xyz-undionly.kpxe)| DHCP boot image file, use if you have NIC issues|
-|EFI| [netboot.xyz.efi](https://boot.netboot.xyz/ipxe/netboot.xyz.efi)| EFI boot image file|
-
-SHA256 checksums are generated during each build of iPXE and are located [here](https://boot.netboot.xyz/ipxe/netboot.xyz-sha256-checksums.txt).  You can also view the scripts that are embedded into the images [here](https://github.com/antonym/netboot.xyz/tree/master/ipxe/disks).
-
-### What is netboot.xyz?
-
-[netboot.xyz](http://netboot.xyz) is a way to select various operating system installers or utilities from one place within the BIOS without the need of having to go retrieve the media to run the tool.  [iPXE](http://ipxe.org/) is used to provide a user friendly menu from within the BIOS that lets you easily choose the operating system you want along with any specific types of versions or bootable flags.
-
-You can remote attach the ISO to servers, set it up as a rescue option in Grub, or even set up your home network to boot to it by default so that it's always available.
-
-### Getting started
-
-Download the bootloader of your choice from the links above and add it to your favorite virtualization tool to start testing out netboot.xyz.  These are precompiled versions of the latest version of [iPXE](https://github.com/ipxe/ipxe) that will chainload you to [https://boot.netboot.xyz](https://boot.netboot.xyz).  If you have DHCP it'll automatically attempt to boot from DHCP.  If you need to set a static IP address, hit the 'm' key during boot up for the failsafe menu and choose manual network configuration.
-
-If you already have iPXE up and running on the network, you can hit netboot.xyz at anytime by typing:
-
-    chain --autofree https://boot.netboot.xyz
-
-You'll need to make sure to have [DOWNLOAD_PROTO_HTTPS](https://github.com/ipxe/ipxe/blob/master/src/config/general.h#L57) enabled when compiling iPXE.
-
-### Operating Systems
-
-#### What Operating Systems are currently available on netboot.xyz?
-
-* [Alpine Linux](https://alpinelinux.org)
-* [Arch Linux](https://www.archlinux.org)
-* [CentOS](https://centos.org)
-* [Debian](https://debian.org)
-* [Devuan](https://devuan.org)
-* [Fedora](https://fedoraproject.org)
-* [Flatcar Linux](https://www.flatcar-linux.org)
-* [FreeBSD](https://freebsd.org)
-* [FreeDOS](http://www.freedos.org)
-* [Gentoo](https://gentoo.org)
-* [IPFire](https://www.ipfire.org)
-* [Mageia](http://www.mageia.org)
-* [Microsoft Windows](https://www.microsoft.com)
-* [MirOS](https://www.mirbsd.org)
-* [NixOS](https://nixos.org)
-* [OpenBSD](http://openbsd.org)
-* [OpenSUSE](http://opensuse.org)
-* [RancherOS](http://rancher.com/rancher-os/)
-* [Red Hat Enterprise Linux](https://www.redhat.com/)
-* [Scientific Linux](http://scientificlinux.org)
-* [Tiny Core Linux](http://tinycorelinux.net)
-* [Ubuntu](http://www.ubuntu.com/)
-
-#### Security Related
-
-* [BlackArch Linux](https://blackarch.org)
-* [Kali Linux](https://www.kali.org)
-* [Parrot Security](https://www.parrotsec.org)
-
-#### Utilities
-
-* [ALT Linux Rescue](https://en.altlinux.org/Rescue)
-* [AVG Rescue CD](http://www.avg.com/us-en/avg-rescue-cd)
-* [Breakin](http://www.advancedclustering.com/products/software/breakin/)
-* [Clonezilla](http://www.clonezilla.org/)
-* [DBAN](http://www.dban.org/)
-* [GParted](http://gparted.org)
-* [Grml](http://grml.org)
-* [Memtest](http://www.memtest.org/)
-* [Super Grub2 Disk](http://www.supergrubdisk.org)
-* [SystemRescueCD](https://www.system-rescue-cd.org)
-* [Ultimate Boot CD](http://www.ultimatebootcd.com)
-
-### Source Code
-
-The source code for netboot.xyz is located [here](https://github.com/antonym/netboot.xyz).
-
-### Contributing
-
-New version of an operating system out?  Found one that network boots well with iPXE?  Pull requests are welcomed and encouraged and helps me out a ton!  Feel free to issue a pull request for new versions or tools that you might find useful.  Once merged into master, [Travis CI](https://travis-ci.org/antonym/netboot.xyz) will regenerate new versions of [iPXE from upstream](https://github.com/ipxe/ipxe) and deploy the latest changes to netboot.xyz.  See more on contributing [here](https://netboot.xyz/contributing).
-
-### Testing New Branches
-
-Under the **Utilities** menu on netboot.xyz, there's an option for ["Test netboot.xyz branch"](https://github.com/antonym/netboot.xyz/blob/master/src/utils.ipxe#L157).  If you've forked the code and have developed a new feature branch, you can use this option to chainload into that branch to test and validate the code.  All you need to do is specify your Github user name and the name of your branch or abbreviated hash of the commit. Also, disable the signature verification for *netboot.xyz* under **Signatures Checks**.
-
-### Feedback
-
-Feel free to open up an [issue](https://github.com/antonym/netboot.xyz/issues) on Github, swing by [Freenode IRC](http://freenode.net/) in the [#netbootxyz](http://webchat.freenode.net/?channels=#netbootxyz) channel, or ping us on [Discord](https://discord.gg/An6PA2a).  Follow us on [Twitter](https://twitter.com/netbootxyz) or like us on [Facebook](https://www.facebook.com/netboot.xyz)!

docs/usage-digitalocean.md

@@ -1,48 +0,0 @@
-# DigitalOcean
-
-[DigitalOcean](https://m.do.co/c/ab4e8f17ba0d) at one point had iPXE support loaded within their SeaBIOS but has since removed it.  In order to get around this, we'll have to rely on the Grub bootloader instead.
-
-iPXE generates linux bootable kernels so that you can boot iPXE directly from Grub.  It then treats the initrd as an embedded script which contains your networking and details to load up netboot.xyz.
-
-Tests were done using a [Fedora 23](https://getfedora.org) instance on [DigitalOcean](https://m.do.co/c/ab4e8f17ba0d).
-
-### Download an iPXE linux kernel
-
-Obtain an iPXE generic kernel [here](https://boot.netboot.xyz/ipxe/generic-ipxe.lkrn) or [compile your own](http://ipxe.org/download) and save it to /boot/generic-ipxe.lkrn.
-
-### Create a netboot.xyz initrd file
-
-The netboot.xyz initrd file contains the script necessary to bring the instance on the network and reach out to netboot.xyz.
-
-Save as /boot/netboot.xyz-initrd (replace your networking information where appropriate):
-
-    #!ipxe
-    #/boot/netboot.xyz-initrd
-    imgfree
-    set net0/ip <instance public ip>
-    set net0/netmask <instance public netmask>
-    set net0/gateway <instance public gateway>
-    set dns <instance dns address>
-    ifopen net0
-    chain --autofree https://boot.netboot.xyz
-
-### Add a Grub2 custom entry
-
-Add the following entry to /etc/grub.d/40_custom:
-
-    #/etc/grub.d/40_custom
-    menuentry 'netboot.xyz' {
-        set root='hd0,msdos1'
-        linux16 /boot/generic-ipxe.lkrn
-        initrd16 /boot/netboot.xyz-initrd
-    }
-
-### Regenerate your grub config
-
-Run grub2-mkconfig right after editing the configuration to add the netboot.xyz entry to your grub menu:
-
-    grub2-mkconfig -o /boot/grub2/grub.cfg
-
-Load up a console and then reboot from the instance to catch the menu option.  You can also change the default boot to netboot.xyz or increase the timeout if you want to be able to catch it easier.
-
-

docs/usage-gce.md

@@ -1,77 +0,0 @@
-# Google Compute Engine (GCE)
-
-## Using with netboot.xyz
-
-**Experimental, currently doesn't work on any images that utilize memdisk as console output cannot be altered.**
-
-*Note: Functionality will be limited as the console is Serial Over Lan.  Distros that utilize memdisk may not provide output while other distros that are retrieved via kernel allow for altering of the console settings during load.  This includes most of the utility tools.  I'll probably look at filtering out options that don't work in the future.  Console may work during the install but may stop working on first boot if it's not set during the install.*
-
-### Create a Bucket
-
-Set a name for your bucket and select the regional storage class.
-
-Upload the netboot.xyz-gce image from this [link](https://boot.netboot.xyz/ipxe/netboot.xyz-gce.tar.gz) to the root of your bucket.
-
-    gsutil cp $tmp/$image_name.tar.gz gs://$gs_bucket
-
-### Create an image
-
-Using the gcloud utility or the Google Cloud Shell, create an image from the iPXE disk you uploaded in the previous step:
-
-    gcloud compute images create $image_name --source-uri gs://$gs_bucket/$image_name.tar.gz
-
-### Boot an instance
-
-Start an instance from the image you created, make sure to enable the serial-port:
-
-    gcloud compute instances create $instance_name --image $image_name --metadata serial-port-enable=1
-
-### Connect to the Instance over Serial Console
-
-    gcloud beta compute connect-to-serial-port $instance_name
-
-From here you should see the netboot.xyz menu and that's probably all you'll be able to do at this point. :)
-
-### Configuring the Instance
-
-In the event DHCP does not work, you'll need to set the static IP address during install time.  You can view this by going into instance details in the console, and clicking on default under network.  You'll need to set the internal IP of the instance along with the subnet and gateway on that page.
-
-### Notes
-
-Here are some notes on how the iPXE image is created in case you want to play around with vanilla iPXE in GCE.
-
-See the iPXE commit [here](https://github.com/ipxe/ipxe/commit/de85336abb7861e4ea4df2e296eb33d179c7c9bd) for more info of GCE support in iPXE.
-
-To create a usable image for GCE:
-
-    make bin/ipxe.usb CONFIG=cloud EMBED=$tmp/main.ipxe
-    cp -f bin/ipxe.usb $tmp/disk.raw
-    ( cd $tmp; tar Sczvf $image_name.tar.gz disk.raw )
-
-To get the installers to work to output serial, when the GCE disk is detected, the console on the kernel command line is set to:
-
-    console=ttyS0,115200n8
-
-## Using without netboot.xyz (standard iPXE)
-
-When building your script, you will want it to look something like this:
-
-    #!ipxe
-
-    echo Google Compute Engine - iPXE boot via metadata
-    ifstat ||
-    dhcp ||
-    route ||
-    chain -ar http://metadata.google.internal/computeMetadata/v1/instance/attributes/ipxeboot
-
-Then when provisioning your instance, you can specify your custom iPXE script file:
-
-    # Create shared boot image
-    make bin/ipxe.usb CONFIG=cloud EMBED=config/cloud/gce.ipxe
-
-    # Configure per-instance boot script
-    gcloud compute instances add-metadata <instance> \
-           --metadata-from-file ipxeboot=boot.ipxe
-
-This lets your custom compiled iPXE boot and then immediately chain to your
-custom iPXE script.

docs/usage-openstack.md

@@ -1,108 +0,0 @@
-# OpenStack
-
-**Experimental, haven't had a chance to run through this recently so YMMV.**
-
-The netboot.xyz ISO image can be used with OpenStack clouds to boot an instance
-and perform a custom installation of an operating system.
-
-### Command line
-
-Start by downloading the ISO and then import it into glance:
-
-    $ wget https://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.iso
-    $ glance image-create --name netboot.xyz \
-        --disk-format iso \
-        --container-format bare \
-        --file netboot.xyz-dhcp.iso \
-        --visibility public
-    +------------------+--------------------------------------+
-    | Property         | Value                                |
-    +------------------+--------------------------------------+
-    | checksum         | 45cdcb89576b6c05598b11585aef46bc     |
-    | container_format | bare                                 |
-    | created_at       | 2016-01-27T20:02:06Z                 |
-    | disk_format      | iso                                  |
-    | id               | 4f11d49e-157b-4740-87ad-db7d59bb5d6d |
-    | min_disk         | 0                                    |
-    | min_ram          | 0                                    |
-    | name             | netboot.xyz                          |
-    | owner            | fbfce4cb346c4f9097a977c54904cafd     |
-    | protected        | False                                |
-    | size             | 1048576                              |
-    | status           | active                               |
-    | tags             | []                                   |
-    | updated_at       | 2016-01-27T20:02:04Z                 |
-    | virtual_size     | None                                 |
-    | visibility       | public                               |
-    +------------------+--------------------------------------+
-
-It should only take a few seconds to import.  Take the UUID from the `id` field
-returned by glance and verify that the image imported successfully:
-
-    $ glance image-show 4f11d49e-157b-4740-87ad-db7d59bb5d6d
-    +------------------+--------------------------------------+
-    | Property         | Value                                |
-    +------------------+--------------------------------------+
-    | checksum         | 45cdcb89576b6c05598b11585aef46bc     |
-    | container_format | bare                                 |
-    | created_at       | 2016-01-27T20:02:06Z                 |
-    | disk_format      | iso                                  |
-    | id               | 4f11d49e-157b-4740-87ad-db7d59bb5d6d |
-    | min_disk         | 0                                    |
-    | min_ram          | 0                                    |
-    | name             | netboot.xyz                          |
-    | owner            | fbfce4cb346c4f9097a977c54904cafd     |
-    | protected        | False                                |
-    | size             | 1048576                              |
-    | status           | active                               |
-    | tags             | []                                   |
-    | updated_at       | 2016-01-27T20:02:04Z                 |
-    | virtual_size     | None                                 |
-    | visibility       | public                               |
-    +------------------+--------------------------------------+
-
-The image has a status of `active`, so we know that glance imported it
-properly.
-
-Let's boot a new instance with this ISO:
-
-    nova boot --flavor m1.small \
-        --image <image-uuid-of-netbootxyz-image> \
-        --nic net-id=<network-uuid> \
-        netbootxyz-testing
-
-Wait about 30 seconds, then request a console URL:
-
-    nova get-spice-console c4ff017e-1234-4053-b740-e83eade277b9 spice-html5
-
-Open the console URL that nova returns and you should see the familiar
-netboot.xyz iPXE interface in the spice console!
-
-### Horizon
-
-Start by [downloading the netboot.xyz ISO](https://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.iso)
-to your local workstation.  Follow these steps to import the image into your
-OpenStack cloud using Horizon:
-
-* Click the _Compute_ tab on the left side, then click _Images_
-* Click _Create Image_ (top right)
-    * Name: `netboot.xyz ISO`
-    * Image Source: Image File
-    * Image File: (browse to the ISO you downloaded)
-    * Format: ISO - Optical Disk Image
-    * Public: Checked (optional, but recommended if you want other tenants to use
-   it)
-* Click _Create Image_
-
-Wait a moment for the status to become `active`. This should only take a few
-seconds.  To boot an instance with the ISO you uploaded, be sure to choose
-_Boot from image_ and select _netboot.xyz ISO_ from the drop down list.
-Configure networking and security groups as you normally would for any other
-instance.
-
-When the instance has fully built and gone to active status, click on the
-instance name and then go to the _Console_ tab. Depending on your browser,
-you may need to click the link to show only the console.
-
-At that point, you should be able to view the netboot.xyz iPXE menu and install
-your operating system.

docs/usage-packet.md

@@ -1,47 +0,0 @@
-# Packet
-
-[Packet](https://packet.net) fully supports netboot.xyz with its Custom iPXE
-operating system.
-
-### Usage
-
-Select the "Custom iPXE" operating system from the portal, or the `custom_ipxe`
-slug when using the API. 
-
-### Provisioning
-
-Put the netboot.xyz URL in the text field that appears in the portal, or use the
-`ipxe_script_url` parameter when creating the device via the API.
-
-    https://boot.netboot.xyz
-
-Press "Deploy" to provision your device. It will take 2-3 minutes for the device
-to become active. Once it's online, connect to Packet's out-of-band serial-over-SSH
-service (S.O.S.) using the device's `id` and the facility where the device was
-deployed, e.g. `ewr1`.
-
-    ssh <device-id>@sos.<facility-code>.packet.net
-
-The current list of facilities is [here](https://www.packet.net/locations/). The
-netboot.xyz iPXE menu will appear and you can complete installation from there.
-
-> **Please Note:** By default, devices are set to boot from the local disk. During
-> provisioning, Packet sets the next boot to PXE. This happens once, which means that
-> if you don't install an operating system before rebooting, it won't reload the
-> netboot.xyz menu. However, you can set your device to always boot to iPXE
-> first by enabling that option under 'server actions' through the customer portal.
-
-### Networking
-
-Devices that are provisioned via Custom iPXE will be able to DHCP for the life of
-the device; however, Packet recommends configuring networking statically. IP
-address information can be found by querying https://metadata.packet.net/metadata
-from the host.
-
-More information on how Packet configures bonding can be found
-[here](https://www.packet.net/help/kb/how-does-the-packet-bonded-network-interface-work/).
-
-Nameservers should be configured as:
-
-    nameserver 147.75.207.207
-    nameserver 147.75.207.208

docs/usage-rackspace.md

@@ -1,5 +0,0 @@
-# Rackspace
-
-See [boot.rackspace.com](http://boot.rackspace.com) for now.  You can chain to netboot.xyz from there:
-
-    chain --autofree https://boot.netboot.xyz

docs/usage-vultr.md

@@ -1,51 +0,0 @@
-# Vultr
-
-[Vultr](http://www.vultr.com/?ref=6870843) has some great support for using
-netboot.xyz right out of the box.
-
-### Boot from ISO
-
-Once you've logged into the console, select ISOs.  In the remote URLs box,
-enter in the URL of a netboot.xyz ISO and press upload:
-
-    https://boot.netboot.xyz/ipxe/netboot.xyz.iso
-
-Go back to the main console screen and press "Deploy New Instance". Follow
-these steps:
-
-* Select _Custom_ for the operating system
-* Select the ISO you uploaded
-* Click _Place Order_
-
-The instance should be online in a few minutes.  Once it's online, go to the
-main account page that lists all of your instances.  Click _Manage_ next to the
-instance you just launched, and then click _View Console_ under
-_Server Actions_. When the console appears, you should see the netboot.xyz
-iPXE menu.
-
-When you've completed the OS installation, select _Custom ISO_ from the Server
-Manager page and click _Remove ISO_.  The ISO will be removed from your
-instance and it will reboot.
-
-### Boot from iPXE Chain URL
-
-Using an iPXE chain url may be easier for some users.  Follow these steps:
-
-* Click _Deploy New Instance_
-* Select _Custom_ for the operating system
-* Select _iPXE_ in the Virtual ISO section
-* Set the chain URL to `https://boot.netboot.xyz`
-* Click _Place Order_
-
-The instance will boot within a few minutes.  Once it boots, you'll have five
-minutes to launch a console and choose an option from the netboot.xyz menu:
-
-* Go back to your account home page with your instances listed
-* Click _Manage_ next to the instance you just launched
-* Click _View Console_ in the _Server Actions_ section
-* Choose the OS you want to deploy in the netboot.xyz menu
-* Complete the OS installation
-
-Once you've finished the installation, reboot the instance as you normally
-would.  Vultr will automatically reboot your virtual machine into the OS you
-deployed.

mkdocs.yml

@@ -1,28 +0,0 @@
-site_name: netboot.xyz
-site_description: netboot.xyz uses iPXE to network boot Operating System installers and utilities from an easy to use menu.
-site_author: netboot.xyz
-site_url: https://netboot.xyz
-repo_url: https://github.com/antonym/netboot.xyz
-copyright: © 2018 <a href="https://twitter.com/@ntonym">Antony Messerli</a>
-docs_dir: docs
-google_analytics: ['UA-68807-15', 'netboot.xyz']
-pages:
-- Home: 'index.md'
-- Boot from...:
-#    - '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'
-- Provider Usage:
-    - 'Digital Ocean': 'usage-digitalocean.md'
-    - 'Google Compute Engine': 'usage-gce.md'
-    - 'OpenStack': 'usage-openstack.md'
-    - 'Packet': 'usage-packet.md'
-    - 'Rackspace': 'usage-rackspace.md'
-    - 'Vultr': 'usage-vultr.md'
-- FAQ: 'faq.md'
-- Contributing: 'contributing.md'
-theme: yeti