Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
screenshots [2007/08/06 21:34] mcb30 |
screenshots [2007/08/12 09:22] (current) mcb30 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Screenshots ====== | ====== Screenshots ====== | ||
| - | === HTTP booting and initramfs assembly === | + | ==== HTTP booting and initramfs assembly ==== |
| You can boot a Linux kernel directly from a web server using gPXE. The kernel, initial ramdisk and other boot-time files (e.g. kernel modules for the network card) can also be loaded from the same web server. There is no need to create dedicated ramdisk images containing drivers for each network card you want to be able to boot from. | You can boot a Linux kernel directly from a web server using gPXE. The kernel, initial ramdisk and other boot-time files (e.g. kernel modules for the network card) can also be loaded from the same web server. There is no need to create dedicated ramdisk images containing drivers for each network card you want to be able to boot from. | ||
| Line 14: | Line 14: | ||
| - | === iSCSI booting Windows Server 2003 === | + | ==== iSCSI booting Windows Server 2003 ==== |
| It is possible to boot Windows Server 2003 from an iSCSI disk using gPXE. This provides a direct replacement for commercial products such as winBoot/i. | It is possible to boot Windows Server 2003 from an iSCSI disk using gPXE. This provides a direct replacement for commercial products such as winBoot/i. | ||
| Line 23: | Line 23: | ||
| - | === AoE booting Windows XP === | + | ==== AoE booting Windows XP ==== |
| You can boot Windows XP from an ATA-over-Ethernet (AoE) disk using gPXE: | You can boot Windows XP from an ATA-over-Ethernet (AoE) disk using gPXE: | ||
| Line 30: | Line 30: | ||
| - | === Configuration UI === | + | ==== Command line ==== |
| + | |||
| + | {{ screenshots/gpxe-cmdline.png?320x200|Command line}} | ||
| + | |||
| + | gPXE has a command shell built in, which allows you to interact with the system and run commands even before the DHCP request takes place. You can assign IP addresses, check network interface statistics, manually download files, and so on. | ||
| + | |||
| + | gPXE also supports script files, which are just sequences of commands; a typical script might look something like | ||
| + | |||
| + | #!gpxe | ||
| + | |||
| + | kernel http://www.etherboot.org/boot/vmlinuz vga=788 | ||
| + | initrd http://www.etherboot.org/boot/initrd.img | ||
| + | boot | ||
| + | |||
| + | |||
| + | |||
| + | ==== Configuration UI ==== | ||
| gPXE allows you to store settings in the NIC EEPROM. Though most network configuration is handed out via DHCP, it can be useful to be able to store certain information (such as iSCSI login usernames and passwords) on the NIC itself. | gPXE allows you to store settings in the NIC EEPROM. Though most network configuration is handed out via DHCP, it can be useful to be able to store certain information (such as iSCSI login usernames and passwords) on the NIC itself. | ||
