PXE only requires a PXE-capable BIOS. PXE will load the pxe boot code
via TFTP and the boot code will use PXE BIOS calls to load additional
modules (e.g. the 'kernel') via TFTP.
It is possible to completely automate the operation, since you ultimately
have control over both the first stage boot code that PXE loads and the
kernel that it loads after that (which could be a second-stage boot or
a real kernel or whatever).
But, of course, it's definitely a major advantage to have a video
console for experimentation :-)
Ah yes, I added the word "network" at the last moment.
Either your motherboard or an add-on card must support the PXE BIOS. Kind of
For more than experimentation - I want to turn off PXE boot so that the reboot
after install doesn't try to reinstall... (And no, I'd rather not rely on a
correctly configured network boot image to tell the client to go boot off the
disk after all.)
"Tigers will do ANYTHING for a tuna fish sandwich."
"We're kind of stupid that way." *munch* *munch*