This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
download [2015/11/24 11:45] robinsmidsrod Bump requirement of binutils to 2.18 because of .reloc usage |
download [2018/07/05 21:33] mcb30 |
||
---|---|---|---|
Line 22: | Line 22: | ||
* make | * make | ||
* perl | * perl | ||
- | * syslinux (for isolinux, only needed for building .iso images) | ||
* liblzma or xz header files | * liblzma or xz header files | ||
- | * zlib, binutils and libiberty header files (only needed for EFI builds) | + | * mtools |
+ | * mkisofs (needed only for building .iso images) | ||
+ | * syslinux (for isolinux, needed only for building .iso images) | ||
===== Choosing what to build ===== | ===== Choosing what to build ===== | ||
Line 52: | Line 53: | ||
==== Chainloading from an existing PXE ROM ==== | ==== Chainloading from an existing PXE ROM ==== | ||
- | {{ :clipart:chain.jpeg?200x96|A chain}} | + | {{ :clipart:chain.jpeg?200x120|A chain}} |
You can chainload iPXE from an existing PXE ROM. This is useful if you have a large number of machines that you want to be able to boot using iPXE, but you do not want to reflash the network card on each individual machine. | You can chainload iPXE from an existing PXE ROM. This is useful if you have a large number of machines that you want to be able to boot using iPXE, but you do not want to reflash the network card on each individual machine. |