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
httpboot [2009/12/20 11:35]
sha0 PXELINUX 210 option
httpboot [2010/10/14 04:39]
dali
Line 1: Line 1:
 ====== HTTP booting ====== ====== HTTP booting ======
- 
-{{ screenshots/​uniboot1.png?​360x200|Linux booting via HTTP}} 
  
 Booting from HTTP with gPXE is as simple as replacing the DHCP filename field with an %%http://%% URL.  For example, if you currently have ///​etc/​dhcpd.conf//​ containing Booting from HTTP with gPXE is as simple as replacing the DHCP filename field with an %%http://%% URL.  For example, if you currently have ///​etc/​dhcpd.conf//​ containing
Line 11: Line 9:
  
     filename "​http://​my.web.server/​pxe.0";​     filename "​http://​my.web.server/​pxe.0";​
 +
 +{{ screenshots/​uniboot1.png?​360x200|Linux booting via HTTP}}
  
 ===== Scalability ===== ===== Scalability =====
  
 HTTP can handle much larger files than TFTP, and scale to much larger distances. ​ You can easily download multi-megabyte files, such as a Linux kernel and a root filesystem, and you can download from servers that are not on your local area network. ​ We have successfully tested booting across the Atlantic using HTTP! HTTP can handle much larger files than TFTP, and scale to much larger distances. ​ You can easily download multi-megabyte files, such as a Linux kernel and a root filesystem, and you can download from servers that are not on your local area network. ​ We have successfully tested booting across the Atlantic using HTTP!
- 
 ===== Using PXELINUX ===== ===== Using PXELINUX =====
  
Line 27: Line 26:
     echo Performing DHCP on first network interface     echo Performing DHCP on first network interface
     dhcp net0     dhcp net0
-    set 210:string http://webserver.com/ +    ​set 209:string pxelinux.cfg/​default 
-    echo Set PXELINUX prefix to use ${210:​string} +    ​set 210:string http://example.com/
-    echo Chaining PXELINUX+
     chain ${210:​string}pxelinux.0     chain ${210:​string}pxelinux.0
  
-The '​chain'​ command above will be expanded by gPXE to 'chain http://webserver.com/​pxelinux.0' ​and the chained-to PXELINUX will look for its configuration file using that prefix. ​ All relative paths specified in the PXELINUX configuration file will also have this prefix prepended to them.+The '​chain'​ command above will be expanded by gPXE to
 +  ​chain http://example.com/​pxelinux.0 
 +and the chained-to PXELINUX will look for its configuration file using the 210 prefix. 
 +All relative paths specified in the PXELINUX configuration file will also have this prefix 
 +prepended to them. 
 + 
 +===== Using gpxelinux.0 ===== 
 + 
 +Since SYSLINUX 3.85 there is also the option of using gpxelinux.0 with pxelinux.0 embedded, example: 
 +<code text> 
 +#!gpxe 
 +echo Performing DHCP on first network interface 
 +dhcp net0 
 +set 209:string pxelinux.cfg/​default 
 +set 210:string http://​example.com/​ 
 +imgload pxelinux.0 
 +boot pxelinux.0 
 +</​code>​ 

QR Code
QR Code httpboot (generated for current page)