HOW IT WORKS


	At this stage we have the three elements necessary to perform a remote
	install: DHCP, TFTP , FTP(*) and NFS. We also should have all the files
	necessary to install with.

	We can now focus on the elements necessary to tie all these together
	into a complete installation process.

	When we first boot our server, assuming PXE is the first boot method,
	the box will first broadcast out over the local lan for a DHCP server.
	The DHCP server should reply with a DHCP lease including the server
	the pxe driver is to be fetched from.

	The client now does the following:

		fetches via tftp the pxe driver
		pxe driver is loaded
		boot configuration is downloaded
		kernel is downloaded based on boot configuration
		mfsroot is downloaded and mounted
		system boots kernel
		system runs init, which detects install.cfg in the root partition
	  	 and runs the installer, sysinstall
		sysinstall runs and performs actions in the install.cfg 
		disk is partitioned, packages are installed and postinstall scripts
	 	 are executed.
		install finishes and system automatically reboots.

	When the system reboots keep in mind your boot order. This is where things
	can get tricky. If the system is configured to boot PXE first then we will
	be stuck in a installer loop UNLESS you disable dhcp or tftp. I disable dhcp
	myself. Otherwise you can have your system boot the harddrive first, then
	PXE but this only applies to systems with formatted drives. If you are
	doing a "nuke & pave" on an existing install we will never get to the PXE
	boot stage. My Dell 600SC offers an option to force PXEBoot from the bios
	splash screen.

	I have not found a good way to have PXE boot and have DHCP fail the PXE
	boot short of turning off DHCP during the reboot.