Classic/“normal” Operating systems, like:
…just need the Interrupt 13 to run and to do file operations, such as:
So, the EtherBoot currently supported protocols:
provide a certain environment level, which is adequate and sufficient to boot the operating systems mentioned above.
New Operating systems, like Windows NT, 2000, XP, 2003 require a more in-depth hard disk environment.
In contrast to the default EtherBoot supported protocols the ATA over Ethernet specification additionally provides/emulates all necessary components for Operating Systems which require an in-depth hard disk / hard disk controller environment[…]
Directory or hard disk (or hard disk image) containg an installed Operating System
| ⇐ network connection
EtherBoot binary with AoE support
Boot priority set to "EtherBoot" in the BIOS setup menu
EtherBoot with AoE support will be used as boot device
EtherBoot with AoE support provides in-depth hard disk environment and loads the Operating System from the harddisk from the AoE Server.
…article will be continued
To get you started, retrieve those files (you will need a RTL8139 card in the client). Setup DHCP reasonably (so the .zpxe file will be loaded). Download the virtual hard drive blade server (or use a real AoE capable drive, of course).
vbladed 0 0 eth0 aoedemo.img
you should be able to boot the client into Fedora.
This is proof-of-concept only, and the code is only in developer codetree yet.