diff options
author | Frans Pop <elendil@planet.nl> | 2006-12-27 04:03:39 +0000 |
---|---|---|
committer | Frans Pop <elendil@planet.nl> | 2006-12-27 04:03:39 +0000 |
commit | 190a18225bcf21fc3b92820fc168a31ab06ec0d7 (patch) | |
tree | 4495f5392797b9e81b812f240beaef7f4dc69980 /nl/install-methods/install-tftp.xml | |
parent | 9d4ef14653ee2e5d098f3f1ad2d9fd2f6f4078fb (diff) | |
download | installation-guide-190a18225bcf21fc3b92820fc168a31ab06ec0d7.zip |
Update of original English docs
Diffstat (limited to 'nl/install-methods/install-tftp.xml')
-rw-r--r-- | nl/install-methods/install-tftp.xml | 63 |
1 files changed, 39 insertions, 24 deletions
diff --git a/nl/install-methods/install-tftp.xml b/nl/install-methods/install-tftp.xml index 2f25c4def..ae6b07c48 100644 --- a/nl/install-methods/install-tftp.xml +++ b/nl/install-methods/install-tftp.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 39614 untranslated --> +<!-- original version: 43558 untranslated --> <sect1 condition="supports-tftp" id="install-tftp"> <title>Preparing Files for TFTP Net Booting</title> @@ -13,26 +13,27 @@ and the machine configured to support booting of your specific machine. </para><para> -You need to setup a TFTP server, and for many machines, a BOOTP server -<phrase condition="supports-rarp">, or RARP server</phrase> -<phrase condition="supports-dhcp">, or DHCP server</phrase>. +You need to setup a TFTP server, and for many machines a DHCP +server<phrase condition="supports-rarp">, or RARP +server</phrase><phrase condition="supports-bootp">, or BOOTP +server</phrase>. </para><para> <phrase condition="supports-rarp">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another -way is to use the BOOTP protocol. </phrase> +way is to use the BOOTP protocol.</phrase> <phrase condition="supports-bootp">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain -a boot image. </phrase> +a boot image.</phrase> -<phrase arch="m68k"> Yet another alternative exists on VMEbus -systems: the IP address can be manually configured in boot ROM. </phrase> +<phrase arch="m68k">Yet another alternative exists on VMEbus +systems: the IP address can be manually configured in boot ROM.</phrase> -<phrase condition="supports-dhcp">The DHCP (Dynamic Host Configuration -Protocol) is a more flexible, backwards-compatible extension of BOOTP. -Some systems can only be configured via DHCP. </phrase> +The DHCP (Dynamic Host Configuration Protocol) is a more flexible, +backwards-compatible extension of BOOTP. +Some systems can only be configured via DHCP. </para><para arch="powerpc"> @@ -101,18 +102,33 @@ tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot Debian packages will in general set this up correctly by default when they are installed. -</para><para> +</para> +<note><para> + +Historically TFTP servers used <filename>/tftpboot</filename> as directory +to serve images from. However, &debian; packages may use other directories +to comply with the <ulink url="&url-fhs-home;">Filesystem Hierarchy +Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default +uses <filename>/var/lib/tftpboot</filename>. You may have to adjust the +configuration examples in this section accordingly. + +</para></note> +<para> + +Look in <filename>/etc/inetd.conf</filename> and remember the directory which +is used as the argument of <command>in.tftpd</command><footnote> -Look in that file and remember the directory which is used as the -argument of <command>in.tftpd</command>; you'll need that below. The -<userinput>-l</userinput> argument enables some versions of +<para> +The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; -this is useful for diagnosing boot errors. If you've had to change -<filename>/etc/inetd.conf</filename>, you'll have to notify the -running <command>inetd</command> process that the file has changed. -On a Debian machine, run <userinput>/etc/init.d/inetd -reload</userinput>; on other machines, -find out the process ID for <command>inetd</command>, and run +this is useful for diagnosing boot errors. +</para> + +</footnote>; you'll need that below. +If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to +notify the running <command>inetd</command> process that the file has changed. +On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on +other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>. </para><para arch="mips"> @@ -146,8 +162,7 @@ to adjust the range of source ports the Linux TFTP server uses. Next, place the TFTP boot image you need, as found in <xref linkend="where-files"/>, in the <command>tftpd</command> -boot image directory. Generally, this directory will be -<filename>/tftpboot</filename>. You'll have to make a link from that +boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards. @@ -166,7 +181,7 @@ images via TFTP itself. For net booting, use the For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure -your dhcp server is configured to pass <filename>/pxelinux.0</filename> +your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot. </para><para arch="ia64"> |