diff --git a/COPYRIGHTS b/COPYRIGHTS index d686b435..342330bb 100644 --- a/COPYRIGHTS +++ b/COPYRIGHTS @@ -1,26 +1,12 @@ +In general iPXE files are licensed under the GPL. For historical +reasons, individual files may contain their own licence declarations. +Most builds of iPXE do not contain all iPXE code (in particular, most +builds will include only one driver), and so the overall licence can +vary depending on what target you are building. -In general gPXE files are licensed under the GPL. GPLed files are in -general either from Linux or have been explicitly put under GPL by the -authors. The license for a file is usually documented at the top of -the file. +The resultant applicable licence(s) for any particular build can be +determined by using "make bin/xxxxxxx.yyy.licence"; for example: -A few files are inherited from FreeBSD netboot and therefore can be -used under BSD or GPL. Documented in this file are some of the -non-GPL'ed files. If the internal documentation for a file disagrees -with what is documented in this file, the internal documentation for -the file shall be override this file. - -File Copyright status - -src/core/misc.c BSD -src/drivers/net/3c509.c BSD -src/drivers/net/3c509.h BSD -src/drivers/net/3c595.c BSD -src/drivers/net/3c595.h BSD -src/drivers/net/3c90x.c Open Source -src/drivers/net/epic100.c None -src/drivers/net/epic100.h None -src/drivers/net/ns8390.c BSD -src/drivers/net/ns8390.h BSD -src/arch/i386/include/bits/string.h None + make bin/rtl8139.rom.licence +to determine the resultant licence(s) for the build bin/rtl8139.rom diff --git a/LOG b/LOG deleted file mode 100644 index d29c8eba..00000000 --- a/LOG +++ /dev/null @@ -1,12 +0,0 @@ -gPXE LOG file - -+ Development for gPXE was moved from SourceForge CVS to a git - repository on git.etherboot.org in the first half of the year 2007. - -+ The gitweb interface for gPXE is available at: - - http://git.etherboot.org/?p=gpxe.git - -+ The gitweb interface largely obsoletes the LOG file that used to be - distributed with Etherboot. - diff --git a/README b/README index b3ae2154..011aa210 100644 --- a/README +++ b/README @@ -1,53 +1,8 @@ -gPXE README File +iPXE README File -gPXE is an implementation of the PXE specification for network -booting, with extensions to allow additional features such as booting -via HTTP, iSCSI, and AoE. - -In generally, gPXE is compatible with the industry-standard PXE -specification, and also supports Etherboot .nbi file loading and some -additional protocols and features. - -For more detailed information about gPXE, please visit our project -website at: http://etherboot.org/ - -BUILDING gPXE IMAGE FROM SOURCE - -If you don't want to install development tools, and have access to the -Web, you can get gPXE and Etherboot ROM images made on demand from -http://rom-o-matic.net/ - -If you would like to compile gPXE images from source, here are some tips. - -We normally compile gPXE images on x86, 32-bit Linux machines. It is -possible to also use x86-64 machines. We use gcc compiler options to -create 32-bit output. - -It is important to have the necessary software packages installed. A gcc-based -toolchain is required. - -The following packages (at least) are required: - - - a gcc tool chain (gcc 3.x or gcc 4.x) - - binutils - - perl - - syslinux - - mtools - -To test your environment, cd to the "src" directory and type: +Quick start guide: + cd src make -You should see a lot of output, and when it stops, the "bin" directory -should be populated with gPXE images and object files. - -To learn more about what to build and how to use gPXE, please visit our -project website at http://etherboot.org/ , particularly the "howto" section. - -CONTACTING US - -Pointers to our project mailing lists are on http://etherboot.org/ - -Real-time help is often available on IRC on the #etherboot channel of -irc.freenode.net. - +For any more detailed instructions, see http://ipxe.org diff --git a/contrib/errcode/README b/contrib/errcode/README index b2963c06..eb66d069 100644 --- a/contrib/errcode/README +++ b/contrib/errcode/README @@ -1,6 +1,6 @@ -Error Code Lookup for gPXE +Error Code Lookup for iPXE ========================== -This program looks up gPXE error codes so you can locate the line of source +This program looks up iPXE error codes so you can locate the line of source code which produced the error. Setup @@ -8,11 +8,11 @@ Setup You must run: ./build_errcodedb.py >errcodedb.py -This extracts error code definitions from the gPXE source code and produces a +This extracts error code definitions from the iPXE source code and produces a "database" which is used by the main program. Once you have done this errcode.py and errcodedb.py are the only files you -need. They are now independent of the gPXE source code and can be moved +need. They are now independent of the iPXE source code and can be moved anywhere. [OPTIONAL] @@ -21,7 +21,7 @@ $ERRCODE_PATH to the errcode.py script. Then move errcode.php to a location visible from your web server. [OPTIONAL] -A simple IRC bot is provided. Edit gpxebot.py to fill in the IRC details. +A simple IRC bot is provided. Edit ipxebot.py to fill in the IRC details. Usage ----- diff --git a/contrib/errcode/build_errcodedb.py b/contrib/errcode/build_errcodedb.py index 1be9d853..99072922 100755 --- a/contrib/errcode/build_errcodedb.py +++ b/contrib/errcode/build_errcodedb.py @@ -18,7 +18,7 @@ import sys import re pxenv_status_files = ('../../src/include/errno.h', ) -errfile_files = ('../../src/include/gpxe/errfile.h', +errfile_files = ('../../src/include/ipxe/errfile.h', '../../src/arch/i386/include/bits/errfile.h') posix_errno_files = ('../../src/include/errno.h', ) diff --git a/contrib/errcode/errcode.php b/contrib/errcode/errcode.php index 87114495..f4774f03 100644 --- a/contrib/errcode/errcode.php +++ b/contrib/errcode/errcode.php @@ -23,7 +23,7 @@ $ERRCODE_PATH = './errcode.py';
-