Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
screenshots [2007/08/03 18:12] mcb30 created |
screenshots [2007/08/12 09:22] (current) mcb30 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Screenshots ====== | ====== Screenshots ====== | ||
| + | ==== 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. | ||
| + | |||
| + | BIOS boot screen, showing gPXE downloading the individual components via HTTP: | ||
| + | |||
| + | {{screenshots/uniboot1.png?360x200|Linux booting via HTTP}} | ||
| + | |||
| + | Booted Linux OS, with network up and running: | ||
| + | |||
| + | {{screenshots/uniboot2.png?400x300|Linux booting via HTTP}} | ||
| + | |||
| + | |||
| + | ==== 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. | ||
| + | |||
| + | Here you can see the Device Manager in Windows Server 2003 showing that the only disk in the system is an "IET VIRTUAL-DISK" attached via iSCSI: | ||
| + | |||
| + | {{screenshots/qemu-win-iscsi-boot-devlist.png?512x384|Windows Server 2003}} | ||
| + | |||
| + | |||
| + | ==== AoE booting Windows XP ==== | ||
| + | |||
| + | You can boot Windows XP from an ATA-over-Ethernet (AoE) disk using gPXE: | ||
| + | |||
| + | {{screenshots/gpxe-xp.png?640x512|Windows XP}} | ||
| + | |||
| + | |||
| + | ==== 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. | ||
| + | |||
| + | A simple configuration user interface is provided: | ||
| + | |||
| + | {{screenshots/gpxe-config-ui.png?320x200|Config UI}} | ||
