You save the above as netboot.ipxe, and you load it from isolinux as an initrd of ipxe.lkrn:
linux16 ipxe.lkrn
initrd netboot.ipxe
(from some date in December and on, iPXE supports scripts as initrds)
In the URL above, the webmaster can maintain a "dists/current" symlink so that "precise" isn't hardcoded.
A better idea would be to load pxelinux.0 instead of directly loading a kernel. This would allow for displaying a vesamenu, with which the user could graphically select from any supported distro series.
Unfortunately that would require a public tftp server, which webmasters may not like. Instead, gpxelinux.0 could do the same over http, but I've never used that.
> I'd love to see your iPXE boot script.
The easiest version is this:
#!ipxe
# We do assume that a DHCP server exists on the local network, e.g. a home router
autoboot
# The rest only happens if no local *boot* server exists archive. ubuntu. com/ubuntu/ dists/precise/ main/installer- i386/current/ images/ netboot/ ubuntu- installer/ i386/linux initrd=initrd.gz archive. ubuntu. com/ubuntu/ dists/precise/ main/installer- i386/current/ images/ netboot/ ubuntu- installer/ i386/initrd. gz
kernel http://
initrd http://
boot
You save the above as netboot.ipxe, and you load it from isolinux as an initrd of ipxe.lkrn:
linux16 ipxe.lkrn
initrd netboot.ipxe
(from some date in December and on, iPXE supports scripts as initrds)
In the URL above, the webmaster can maintain a "dists/current" symlink so that "precise" isn't hardcoded.
A better idea would be to load pxelinux.0 instead of directly loading a kernel. This would allow for displaying a vesamenu, with which the user could graphically select from any supported distro series.
Unfortunately that would require a public tftp server, which webmasters may not like. Instead, gpxelinux.0 could do the same over http, but I've never used that.