MultiNetBoot: Difference between revisions
AlainKnaff (talk | contribs) No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
---- | |||
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | |||
---- | |||
=[http://ehyloxame.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]= | |||
---- | |||
=[http://ehyloxame.co.cc CLICK HERE]= | |||
---- | |||
</div> | |||
= Net boot chosing between multiple systems = | = Net boot chosing between multiple systems = | ||
Nowadays, many systems (Kubuntu, SuSE, Fedora, ...) allow network booting or installing. In order to do this, you usually need to copy a subfolder from the installation CD to your tftp server, and set this as your root. | Nowadays, many systems (Kubuntu, SuSE, Fedora, ...) allow network booting or installing. In order to do this, you usually need to copy a subfolder from the installation CD to your tftp server, and set this as your root. | ||
However, until syslinux 3.72 and its | However, until syslinux 3.72 and its <code>pxechain.com</code> module, it was not easily possible to set up a boot menu allowing to chose among one of many systems. | ||
With | With <code>pxechain.com</code>, it has become very simple to set up a global boot menu, as described below. | ||
== Preparation == | == Preparation == | ||
| Line 11: | Line 19: | ||
* Download syslinux-3.72 (or later) from http://www.kernel.org/pub/linux/utils/boot/syslinux/ | * Download syslinux-3.72 (or later) from http://www.kernel.org/pub/linux/utils/boot/syslinux/ | ||
* Compile it | * Compile it | ||
* Copy | * Copy <code>modules/pxechain.com</code>, <code>com32/menu/menu.c32</code> and <code>core/pxelinux.0</code> to your tftproot (usually <code>/var/lib/tftpboot</code>) | ||
* Set up your DHCP server to point to the pxlinux.0 in your tftp root by putting the following into your | * Set up your DHCP server to point to the pxlinux.0 in your tftp root by putting the following into your <code>dhcpd.conf</code>, and restart it: | ||
<code><pre> | |||
filename | filename "pxelinux.0"; | ||
</pre></code> | |||
== Setting up the various systems you want to chose among == | == Setting up the various systems you want to chose among == | ||
Copy the boot environments of the systems that you want to chose amongst as subdirectories of your tftp root : | Copy the boot environments of the systems that you want to chose amongst as subdirectories of your tftp root : <code>/var/lib/tftpboot/udpcast</code> , <code>/var/lib/tftpboot/kubuntu</code>, ... | ||
== Making index file == | == Making index file == | ||
Set up the root level's PXElinux configuration file to be an index. Create the | Set up the root level's PXElinux configuration file to be an index. Create the <code>/var/lib/tftpbot/pxelinux.cfg</code> directory, and store the following in <code>/var/lib/tftpboot/pxelinux.cfg/default</code> : | ||
<code><pre> | |||
default menu.c32 | default menu.c32 | ||
prompt 0 | prompt 0 | ||
| Line 39: | Line 47: | ||
kernel pxechain.com | kernel pxechain.com | ||
append ::KubuntuNet/pxelinux.0 | append ::KubuntuNet/pxelinux.0 | ||
</pre></code> | |||
For each system you've got one paragraph, starting with a LABEL line (to give it a unique name), followed by a menu line (to set the name displayed in the menu). | For each system you've got one paragraph, starting with a LABEL line (to give it a unique name), followed by a menu line (to set the name displayed in the menu). | ||
The | The <code>kernel pxechain.com</code> line tells pxelinux to chain another pxe boot loader (the one present in the system's image). The last line (<code>append</code> ...) points towards the boot loader of the system to be loaded. | ||
== How it works / why it is needed == | == How it works / why it is needed == | ||
pxechain.com works by patching the DHCP information received from the server such that the boot filename points into the subdirectory of the chosen system (parameter of the | pxechain.com works by patching the DHCP information received from the server such that the boot filename points into the subdirectory of the chosen system (parameter of the <code>append</code> line), rather than the root. | ||
Directly saying | Directly saying <code>kernel udpcast/pxelinux.0</code> would not work: Although the correct <code>pxelinux.0</code> would be loaded, all dependant files (<code>pxelinux.cfg/default</code>, <code>linux</code>, <code>initrd</code>, ...) would again be loaded relatively to the root. Indeed the boot loader derives its "working directory" from the DHCP packet, which would not be patched using this simplistic approach. | ||
Revision as of 04:55, 24 November 2010
Net boot chosing between multiple systems
Nowadays, many systems (Kubuntu, SuSE, Fedora, ...) allow network booting or installing. In order to do this, you usually need to copy a subfolder from the installation CD to your tftp server, and set this as your root.
However, until syslinux 3.72 and its <code>pxechain.com</code> module, it was not easily possible to set up a boot menu allowing to chose among one of many systems.
With <code>pxechain.com</code>, it has become very simple to set up a global boot menu, as described below.
Preparation
- Download syslinux-3.72 (or later) from http://www.kernel.org/pub/linux/utils/boot/syslinux/
- Compile it
- Copy <code>modules/pxechain.com</code>, <code>com32/menu/menu.c32</code> and <code>core/pxelinux.0</code> to your tftproot (usually <code>/var/lib/tftpboot</code>)
- Set up your DHCP server to point to the pxlinux.0 in your tftp root by putting the following into your <code>dhcpd.conf</code>, and restart it:
<code><pre>
filename "pxelinux.0";
</pre></code>
Setting up the various systems you want to chose among
Copy the boot environments of the systems that you want to chose amongst as subdirectories of your tftp root : <code>/var/lib/tftpboot/udpcast</code> , <code>/var/lib/tftpboot/kubuntu</code>, ...
Making index file
Set up the root level's PXElinux configuration file to be an index. Create the <code>/var/lib/tftpbot/pxelinux.cfg</code> directory, and store the following in <code>/var/lib/tftpboot/pxelinux.cfg/default</code> :
<code><pre> default menu.c32 prompt 0 menu title Hitchhiker PXE boot menu
LABEL udpcast
menu label Udpcast
kernel pxechain.com
append ::udpcast/pxelinux.0
LABEL KubuntuNet
menu Kubuntu network install
kernel pxechain.com
append ::KubuntuNet/pxelinux.0
</pre></code>
For each system you've got one paragraph, starting with a LABEL line (to give it a unique name), followed by a menu line (to set the name displayed in the menu). The <code>kernel pxechain.com</code> line tells pxelinux to chain another pxe boot loader (the one present in the system's image). The last line (<code>append</code> ...) points towards the boot loader of the system to be loaded.
How it works / why it is needed
pxechain.com works by patching the DHCP information received from the server such that the boot filename points into the subdirectory of the chosen system (parameter of the <code>append</code> line), rather than the root.
Directly saying <code>kernel udpcast/pxelinux.0</code> would not work: Although the correct <code>pxelinux.0</code> would be loaded, all dependant files (<code>pxelinux.cfg/default</code>, <code>linux</code>, <code>initrd</code>, ...) would again be loaded relatively to the root. Indeed the boot loader derives its "working directory" from the DHCP packet, which would not be patched using this simplistic approach.
