gPXE
DeveloperEtherboot project
Initial release1995, 30–31 years ago[1][2]
Final release
1.0.1 / 16 August 2011; 14 years ago (2011-08-16)
Written inC
TypeBoot loader
LicenseGPLv2+
Websiteetherboot.org
Etherboot Logo
Etherboot Logo

gPXE is an open-source Preboot eXecution Environment (PXE) client firmware implementation and bootloader derived from Etherboot. It can be used to enable computers without built-in PXE support to boot from the network, or to extend an existing client PXE implementation with support for additional protocols. While standard PXE clients use TFTP to transfer data, gPXE client firmware adds the ability to retrieve data through other protocols like HTTP, iSCSI and ATA over Ethernet (AoE), and can work with Wi-Fi rather than requiring a wired connection.

gPXE development ceased in summer 2010,[3] and several projects are migrating[4] or considering migrating[5] to iPXE as a result.

PXE implementation

edit

gPXE can be loaded by a computer in several ways:

gPXE implements its own PXE stack, using a driver corresponding to the network card, or a UNDI driver if it was loaded by PXE itself. This allows to use a PXE stack even if the network card has no boot ROM, by loading gPXE from a fixed medium.

Bootloader

edit

Although its basic role was to implement a PXE stack, gPXE can be used as a full-featured network bootloader. It can fetch files from multiple network protocols,[6] such as TFTP, NFS, HTTP[7][8] or FTP, and can boot PXE, ELF, Linux, FreeBSD, multiboot, EFI, NBI and Windows CE images.

In addition, it is scriptable and can load COMBOOT and COM32 SYSLINUX extensions. This allows for instance to build a graphical menu for network boot.

See also

edit

References

edit
  1. ^ "about — Etherboot/gPXE Wiki".
  2. ^ "Bringing PXE Boot to the 21st Century". Archived from the original on 2012-11-20.
  3. ^ ""gPXE is no longer actively maintained. Users should upgrade to iPXE."". Archived from the original on 2014-04-13. Retrieved 2010-11-30.
  4. ^ Xen ChangeLog showing migration to iPXE because "it is actively maintained"
  5. ^ KVM call minutes showing consideration of migration to iPXE
  6. ^ Google TechTalk demonstrates how to load operating systems from remote servers using gPXE
  7. ^ "Booting your machine over HTTP". Archived from the original on 2010-02-08. Retrieved 2009-12-23.
  8. ^ SliTaz web boot
edit

📚 Artikel Terkait di Wikipedia

IPXE

software and bootloader, created in 2010 as a fork of gPXE (gPXE was named Etherboot until 2008). It can be used to enable computers without built-in PXE capability

Preboot Execution Environment

doi:10.17487/RFC5970. ISSN 2070-1721. RFC 5970. Proposed Standard. "Etherboot/gPXE Wiki". Etherboo.org. "NetBoot 2.0: Boot Server Discovery Protocol

Coreboot

can load any other stand-alone ELF executable, such as iPXE, gPXE or Etherboot that can boot a Linux kernel over a network, or SeaBIOS that can load

Network Bootable Image

legacy format that wraps operating system images to makes it possible for Etherboot to load the images directly. NBI format is able to combine kernel, file

Cromwell (computing)

it runs without Linux) Linux kernel-derived JPEG decompression code Etherboot networking code GRUB filesystem support and bootloader code The standalone

Option ROM

Compaq, Phoenix, & Intel. January 11, 1996. "The execution environment of Etherboot". Salihun, Darmawan (January 9, 2007). BIOS Disassembly Ninjutsu Uncovered

Diskless Remote Boot in Linux

The client computer is set to boot from the network card using PXE or Etherboot. The client requests an IP address, and tftp image to boot from, both

ThinCan

come with either the same RDP client as the original ThinCan or with Etherboot support for UNIX terminal services. DBE61 models come with either a BIOS