GPXE: Difference between revisions

From coreboot
Jump to navigation Jump to search
(Add link to gpxe homepage, and clarify it's okay to use seabios and gpxe together.)
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''GPXE''' is a tool for loading an operating system over a network. See their homepage ( http://etherboot.org/ ) for more information.  GPXE is the successor of [[Etherboot]].
'''[http://etherboot.org/ GPXE]''' is a tool for loading an operating system over a network. GPXE is the successor of [[Etherboot]], it has been superseded by [[IPXE|IPXE]].


GPXE uses legacy bios callbacks, and it works well with [[SeaBIOS]].
GPXE uses legacy BIOS callbacks, and it works well with [[SeaBIOS]].


There are experimental patches to make GPXE work without legacy bios callbacks at: http://whiterocker.com/gpxe/ These patches may be useful if one needs to run GPXE without SeaBIOS.
There are experimental patches to make GPXE work without legacy BIOS callbacks:
 
* http://whiterocker.com/gpxe/.
 
These patches may be useful if one needs to run GPXE without SeaBIOS.


== Building ==
== Building ==
Line 9: Line 13:
TODO
TODO


== See also ==
* [[IPXE|IPXE (which is more recent)]]


{{PD-self}}
{{PD-self}}

Latest revision as of 16:18, 7 October 2012

GPXE is a tool for loading an operating system over a network. GPXE is the successor of Etherboot, it has been superseded by IPXE.

GPXE uses legacy BIOS callbacks, and it works well with SeaBIOS.

There are experimental patches to make GPXE work without legacy BIOS callbacks:

These patches may be useful if one needs to run GPXE without SeaBIOS.

Building

TODO

See also

Public domain I, the copyright holder of this work, hereby release it into the public domain. This applies worldwide.

In case this is not legally possible:
I grant anyone the right to use this work for any purpose, without any conditions, unless such conditions are required by law.