Differences

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

--- download [2007/09/27 06:26]
mcb30
+++ download [2011/09/12 18:58] (current)
mdc [Source code (tarballs)]
@@ Line 1: / Line 1: @@
 ====== Download ======
-==== Download source code ====
+==== 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
-or, if 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 time, use:
-Once you have the code, you can build it using
+  git pull
-  cd gpxe/src
+==== Source code (tarballs) ====
-  make
-This will generate bootable images for floppy disk, CD-ROM, and USB key, which is the best way to get started experimenting with gPXE.
+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://etherboot.org/rel/gpxe/]] or [[http://kernel.org/pub/software/utils/boot/gpxe/]].
-=== Updating source code ===
+==== Extensions in development (gpxe-staging) ====
-To update your downloaded source tree at any time, use
+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.
-  git pull
+==== Building from Source ====
-This will fetch the latest changes and apply them to your tree.  This command will work only if you obtained your source tree using ''git clone''; if you downloaded a tarball then the only way to update your tree is to download a new tarball.
+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
-=== Source code for old versions ===
+**Centos 5 / Fedora 11 Notes**
-Should you want it, the source code for the old Etherboot-5.4 release is available from [[http://git.etherboot.org/?p=etherboot.git]].
+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 incorrect, this has not been tested in other distros. ISOLINUX_BIN config has been missing for a while.
-==== 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.
+=== Etherboot 5.4 and older releases ===
+Source code for Etherboot 5.4 (our legacy bootloader, in 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]]

Trace:

Differences

Navigation

Search

Toolbox

QR Code