>
>>From my experience PXE is not easier to use than coming up with my
> own. At least not for machines that regularly need to network boot.
> And many motherboard manufacturers are happy to replace their PXE
> option rom with an etherboot option rom.
>
> And besides not working well PXE is overly complicated, and
> intricately tied to the x86 BIOS. I would rather simply follow the
> good internet RFC's and work on filling in the one missing piece. A
> file format. And the ELF file format works very well.
>
> Besides all of that of that I regularly network boot LinuxBIOS which
> PXE can't cope with.
>
> Using etherboot I don't need a second stage bootloader. Etherboot
> does work well. I don't need anything beyond vanilla DHCP and TFTP
> (the standards for network booting). The research into how to do it
> has really been done. And I can work on interesting things like
> adding end to end checksums of the image I am booting.
>
Etherboot requires a specific other driver. The problem with what
you're proposing -- and let me get it very clear here, it's a huge
problem -- is that you have no device-independent access to the boot
medium (in this case, the network) once you have loaded the initial boot
program. This is an enormous drawback.
That's the thing with PXE and the BIOS too, for that matter: they might
be specs done by monkeys, but when it really counts, what you need is
really there (modulo bugs, but that applies to everything.)
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/