Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
appnoted [2009/04/22 10:18] yazzy |
appnoted [2009/04/22 10:28] (current) yazzy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ======How to network boot operating systems with gPXE====== | ||
| + | |||
| =====Introduction===== | =====Introduction===== | ||
| gPXE is a new version of the well know Etherboot project.\\ | gPXE is a new version of the well know Etherboot project.\\ | ||
| Line 72: | Line 74: | ||
| I will not be going into details here. This config file is using the "conventional TFTP" configuration with **/home/tftpboot** as it's relative root directory fetching all the files from there.\\ | I will not be going into details here. This config file is using the "conventional TFTP" configuration with **/home/tftpboot** as it's relative root directory fetching all the files from there.\\ | ||
| The subnet definition will hand out IPs for our clients from defined range.\\ | The subnet definition will hand out IPs for our clients from defined range.\\ | ||
| - | PXE booting your client it will first download the gPXE binary which will "take over" from there and download it's own configuration file.\\ | + | When PXE booting your client, it will first download the gPXE binary which will "take over" from there and download it's own configuration file.\\ |
| The **if not exists gpxe.bus-id** option is used to first hand out the undionly.kpxe file to PXE and then the menu.gpxe configuration file to gPXE. | The **if not exists gpxe.bus-id** option is used to first hand out the undionly.kpxe file to PXE and then the menu.gpxe configuration file to gPXE. | ||
