Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
faq [2015/10/24 22:13]
mcb30
faq [2015/10/24 22:13]
mcb30
Line 17: Line 17:
 ===== How does iPXE relate to gPXE and Etherboot? ===== ===== How does iPXE relate to gPXE and Etherboot? =====
  
-iPXE is the official replacement for gPXE((iPXE is developed by the people who originally developed gPXE (which evolved from Etherboot). ​ Unfortunately,​ the [[http://​www.whois.net/​whois/​gpxe.org|gpxe.org]] and [[http://​www.whois.net/​whois/​etherboot.org|etherboot.org]] domains are owned by an individual who wishes to exercise a high degree of control over the project and the codebase, so in April 2010 the decision was taken to [[http://​git.ipxe.org/​ipxe.git/​commit/​8406115|create a new project named iPXE]], using the existing codebase as a starting point. +iPXE is the official replacement for gPXE((iPXE is developed by the people who originally developed gPXE (which evolved from Etherboot). ​ Unfortunately,​ the [[http://​www.whois.net/​whois/​gpxe.org|gpxe.org]] and [[http://​www.whois.net/​whois/​etherboot.org|etherboot.org]] domains are owned by an individual who wishes to exercise a high degree of control over the project and the codebase, so in April 2010 the decision was taken to [[http://​git.ipxe.org/​ipxe.git/​commit/​8406115|create a new project named iPXE]], using the existing codebase as a starting point. ​ Since the two projects diverged, development on gPXE has [[http://​www.ohloh.net/​p/​gpxe/​factoids/​12668529|stopped]]. ​ There have been [[http://​git.etherboot.org/?​p=gpxe.git;​a=commitdiff;​h=c780ec88551e0ecee345025946702aace1dda500|no commits]] to the gPXE tree since 2011.
----- +
-Since the two projects diverged, development on gPXE has [[http://​www.ohloh.net/​p/​gpxe/​factoids/​12668529|stopped]]. ​ There have been [[http://​git.etherboot.org/?​p=gpxe.git;​a=commitdiff;​h=c780ec88551e0ecee345025946702aace1dda500|no commits]] to the gPXE tree since 2011.+
 ---- ----
 In summary: if you are currently using gPXE then you should upgrade to iPXE as soon as is reasonably practical.)) ​ Any feature present in gPXE is also present in iPXE, and users can seamlessly upgrade from gPXE to iPXE. In summary: if you are currently using gPXE then you should upgrade to iPXE as soon as is reasonably practical.)) ​ Any feature present in gPXE is also present in iPXE, and users can seamlessly upgrade from gPXE to iPXE.
faq.txt · Last modified: 2015/10/24 22:14 by mcb30
Recent changes RSS feed CC Attribution-Share Alike 4.0 International Driven by DokuWiki
All uses of this content must include an attribution to the iPXE project and the URL https://ipxe.org
References to "iPXE" may not be altered or removed.