| 112 |
To use the Pre-boot Execution Environment (PXE) method of TFTP |
To use the Pre-boot Execution Environment (PXE) method of TFTP |
| 113 |
booting, you will need a TFTP server with <userinput>tsize</userinput> |
booting, you will need a TFTP server with <userinput>tsize</userinput> |
| 114 |
support. On a &debian; server, the <classname>atftpd</classname> and |
support. On a &debian; server, the <classname>atftpd</classname> and |
| 115 |
<classname>tftpd-hpa</classname> packages qualify. |
<classname>tftpd-hpa</classname> packages qualify; we recommend |
| 116 |
|
<classname>tftpd-hpa</classname>. |
| 117 |
|
|
| 118 |
</para></note><para arch="mips"> |
</para></note><para arch="mips"> |
| 119 |
|
|
| 164 |
<filename>yaboot-netboot.conf</filename>. Just rename this to |
<filename>yaboot-netboot.conf</filename>. Just rename this to |
| 165 |
<filename>yaboot.conf</filename> in the TFTP directory. |
<filename>yaboot.conf</filename> in the TFTP directory. |
| 166 |
|
|
|
</para><para arch="not-powerpc"> |
|
|
|
|
|
Often, the file that the TFTP client will look for is |
|
|
<replaceable>client-ip-in-hexclient-architecture</replaceable>. To |
|
|
compute <replaceable>client-ip-in-hex</replaceable>, take each byte of |
|
|
the client IP address and translate it into hexadecimal notation. If |
|
|
you have a machine handy with the <command>bc</command> program, you |
|
|
can use the program. First issue the <userinput>obase=16</userinput> |
|
|
command to set the output to hex, then enter the individual components |
|
|
of the client IP one at a time. As for |
|
|
<replaceable>client-architecture</replaceable>, try out some values. |
|
|
|
|
|
</para><para arch="i386"> |
|
|
|
|
|
For PXE booting, you can use the boot loader included with |
|
|
<classname>syslinux</classname>: <filename>pxelinux.0</filename>. The boot |
|
|
loader should be copied into the <filename>/tftpboot</filename> |
|
|
folder. Then create a subdirectory within |
|
|
<filename>/tftpboot</filename> named |
|
|
<filename>/tftpboot/pxelinux.cfg</filename>, and within that directory |
|
|
create a text file <filename>default</filename>. Here is an example of |
|
|
a <filename>default</filename> file's contents: |
|
|
|
|
|
<informalexample><screen> |
|
|
|
|
|
default lanlinux |
|
|
prompt 1 |
|
|
|
|
|
label lanlinux |
|
|
kernel vmlinuz |
|
|
append initrd=initrd.gz devfs=mount root=/dev/ram |
|
|
|
|
|
</screen></informalexample> |
|
|
|
|
|
Note that <userinput>devfs=mount</userinput> is important, because without it |
|
|
there may be problems mounting the initrd.gz file system once the |
|
|
kernel is booted. Also note that you may need an additional parameter |
|
|
<userinput>ramdisk_size=<replaceable>size in KB</replaceable></userinput>, |
|
|
depending on the image you are booting. |
|
|
|
|
| 167 |
</para><para arch="i386"> |
</para><para arch="i386"> |
| 168 |
|
|
| 169 |
Finally, copy the <filename>vmlinuz</filename> and |
For PXE booting, everything you should need is set up in the |
| 170 |
<filename>initrd.gz</filename> files (for the netboot installation method) |
<filename>netboot/pxeboot.tar.gz</filename> tarball. Simply extract this |
| 171 |
from the Debian ftp archive into the <filename>/tftpboot</filename> folder, |
tarball into the <command>tftpd</command> boot image directory. |
|
where the bootloader will be looking for them. |
|
| 172 |
|
|
| 173 |
</para> |
</para> |
| 174 |
|
|