summaryrefslogtreecommitdiff
path: root/fi/install-methods/tftp/bootp.xml
diff options
context:
space:
mode:
Diffstat (limited to 'fi/install-methods/tftp/bootp.xml')
-rw-r--r--fi/install-methods/tftp/bootp.xml72
1 files changed, 72 insertions, 0 deletions
diff --git a/fi/install-methods/tftp/bootp.xml b/fi/install-methods/tftp/bootp.xml
new file mode 100644
index 000000000..b6683f0ad
--- /dev/null
+++ b/fi/install-methods/tftp/bootp.xml
@@ -0,0 +1,72 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+
+ <sect2 condition="supports-bootp" id="tftp-bootp">
+ <title>Setting up BOOTP server</title>
+<para>
+
+There are two BOOTP servers available for GNU/Linux, the CMU
+<command>bootpd</command> and the other is actually a DHCP server, ISC
+<command>dhcpd</command>, which are contained in the
+<classname>bootp</classname> and <classname>dhcp</classname> packages
+in &debian;.
+
+</para><para>
+
+To use CMU <command>bootpd</command>, you must first uncomment (or
+add) the relevant line in <filename>/etc/inetd.conf</filename>. On
+&debian;, you can run <userinput>update-inetd --enable
+bootps</userinput>, then <userinput>/etc/init.d/inetd
+reload</userinput> to do so. Elsewhere, the line in question should
+look like:
+
+<informalexample><screen>
+bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120
+</screen></informalexample>
+
+Now, you must create an <filename>/etc/bootptab</filename> file. This
+has the same sort of familiar and cryptic format as the good old BSD
+<filename>printcap</filename>, <filename>termcap</filename>, and
+<filename>disktab</filename> files. See the
+<filename>bootptab</filename> manual page for more information. For
+CMU <command>bootpd</command>, you will need to know the hardware
+(MAC) address of the client. Here is an example
+<filename>/etc/bootptab</filename>:
+
+<informalexample><screen>
+client:\
+ hd=/tftpboot:\
+ bf=tftpboot.img:\
+ ip=192.168.1.90:\
+ sm=255.255.255.0:\
+ sa=192.168.1.1:\
+ ha=0123456789AB:
+</screen></informalexample>
+
+You will need to change at least the <quote>ha</quote> option, which
+specifies the hardware address of the client. The <quote>bf</quote>
+option specifies the file a client should retrieve via TFTP; see
+<xref linkend="tftp-images"/> for more details.
+
+<phrase arch="mips">
+On SGI Indys you can just enter the command monitor and type
+<userinput>printenv</userinput>. The value of the
+<userinput>eaddr</userinput> variable is the machine's MAC address.
+</phrase>
+
+</para><para>
+
+By contrast, setting up BOOTP with ISC <command>dhcpd</command> is
+really easy, because it treats BOOTP clients as a moderately special
+case of DHCP clients. Some architectures require a complex
+configuration for booting clients via BOOTP. If yours is one of
+those, read the section <xref linkend="dhcpd"/>. Otherwise, you
+will probably be able to get away with simply adding the
+<userinput>allow bootp</userinput> directive to the configuration
+block for the subnet containing the client, and restart
+<command>dhcpd</command> with <userinput>/etc/init.d/dhcpd
+restart</userinput>.
+
+</para>
+ </sect2>