Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
download [2007/08/09 20:28]
mcb30
download [2009/08/01 15:23]
mdc
Line 1: Line 1:
 ====== Download ====== ====== Download ======
  
-==== Download source ​====+==== Prebuilt binaries ​====
  
-Source code is now maintained in our git repository ​at [[http://​git.etherboot.org/?​p=gpxe.git]].  You can check out a copy of the source tree using+Prebuilt gPXE images are available from [[http://​rom-o-matic.net/​]]. ​ Images can be generated from official gPXE releases or from the current development tree.  This is probably the easiest way to get started with gPXE. 
 + 
 +==== Source code (git) ==== 
 + 
 +You can browse the current development tree at [[http://​git.etherboot.org/?​p=gpxe.git]], or check out a copy using:
  
   git clone git://​git.etherboot.org/​scm/​gpxe.git   git clone git://​git.etherboot.org/​scm/​gpxe.git
  
-orif you don't have git installed, download a tarball of the current development snapshot from [[http://​git.etherboot.org/?​p=gpxe.git;​a=snapshot]].+To update your checked out copy at any timeuse:
  
-Once you have the code, you can build it using+  git pull
  
-  ​cd src+==== Source code (tarballs) ==== 
 + 
 +If you do not have ''​git''​ installed, you can download a tarball of the current development snapshot of gPXE from [[http://​git.etherboot.org/?​p=gpxe.git;​a=snapshot]] or, a tarball of the most recent official release from  [[http://​kernel.org/​pub/​software/​utils/​boot/​gpxe/​]]. 
 + 
 +==== Extensions in development (gpxe-staging) ==== 
 + 
 +A separate repository is kept for useful gPXE extensions and patches that have not been sufficiently tested and reviewed to be merged into gPXE mainline. See the [[staging|staging page]] if you'd like to help us test them. 
 + 
 +==== Building from Source ==== 
 + 
 +A complete build of gPXE or Etherboot requires the ''​syslinux''​ and ''​mtools''​ packages in your development environment. ​ ''​syslinux''​ is required in order to create ISO images. On RedHat/​Fedora systems you can install these packages using: 
 + 
 +  sudo yum install syslinux mtools 
 + 
 +You can then do a complete build of gPXE using: 
 + 
 +  ​cd gpxe/src
   make   make
  
-This will generate bootable images for floppy diskCD-ROM, and USB keywhich is the best way to get started experimenting with gPXE.+**Centos 5 Notes** 
 + 
 +You may need to set the value in the line 59 of src/​arch/​i386/​Makefile correctly (/​usr/​share/​syslinux/​isolinux.bin)apparently the reference to /​usr/​lib/​syslinux/​isolinux.bin is incorrectthis has not been tested in other distros. ISOLINUX_BIN config has been missing for a while. 
 + 
 +---- 
 + 
 +=== Etherboot 5.4 and older releases === 
 + 
 +Source code for Etherboot 5.4 (our legacy bootloaderin maintenance-only mode) is available at [[http://​git.etherboot.org/?​p=etherboot.git]]. 
 + 
 +The source code for older Etherboot releases is available from [[http://​sourceforge.net/​project/​showfiles.php?​group_id=4233&​package_id=4250]] 
  
-The source code for the old Etherboot-5.4 release is available from [[http://​git.etherboot.org/?​p=etherboot.git]]. 
  
-==== Download pre-built binaries ==== 
  
-You can get pre-built ROM images from [[http://​rom-o-matic.net/​]]. ​ At the moment, only Etherboot 5.4 ROMs are available; gPXE ROMs will be available shortly. 
  

QR Code
QR Code download (generated for current page)