Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
appnoted [2009/04/22 05:26] yazzy created |
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 6: | Line 8: | ||
| =====Required software===== | =====Required software===== | ||
| - | Software used for this howto: | + | Software used in this HowTo: |
| *Ubuntu Linux 9.04 | *Ubuntu Linux 9.04 | ||
| Line 13: | Line 15: | ||
| *Internet Systems Consortium DHCP server V3.1.1 - http://www.isc.org | *Internet Systems Consortium DHCP server V3.1.1 - http://www.isc.org | ||
| *TFTP server from Linux NetKit - http://www.h cs.harvard.edu/~dholland/computers/netkit.html | *TFTP server from Linux NetKit - http://www.h cs.harvard.edu/~dholland/computers/netkit.html | ||
| + | |||
| + | |||
| + | **NOTE**: Although I used Linux in this HowTo you can use any O.S running DHCP and TFTP servers to make this work.\\ | ||
| + | My boot server at home runs NetBSD and works great with this setup. All you need is compiled gPXE binary. | ||
| Line 68: | 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. | ||
| Line 158: | Line 164: | ||
| Boot your computer using PXE network booting.\\ | Boot your computer using PXE network booting.\\ | ||
| If all went you should be able to see message about DHCP address and then gPXE will get downloaded and show a menu on your screen. | If all went you should be able to see message about DHCP address and then gPXE will get downloaded and show a menu on your screen. | ||
| + | |||
| + | |||
| + | ===== Screenshots ===== | ||
| + | |||
| + | And some screenshots. Loading of gPXE with VirtualBox : | ||
| + | |||
| + | Initial boot with PXE/gPXE:\\ | ||
| + | {{:gpxe-initial.png|}} | ||
| + | |||
| + | An example of gPXE menu:\\ | ||
| + | {{:gpxe-menu.png|}} | ||
| Line 169: | Line 186: | ||
| That's all folks! | That's all folks! | ||
| \\ | \\ | ||
| - | [[User:YazzY|YazzY]] | + | [[User:YazzY|Marcin Jessa]] |
