summaryrefslogtreecommitdiff
path: root/da/install-methods/tftp/bootp.xml
diff options
context:
space:
mode:
authorFrans Pop <elendil@planet.nl>2009-08-22 15:52:14 +0000
committerFrans Pop <elendil@planet.nl>2009-08-22 15:52:14 +0000
commit325e7229b079ce8367df7a7571aad8bfc8e1e5a9 (patch)
treeef067b19e0513da5d71136e123a5ee504ccc9f58 /da/install-methods/tftp/bootp.xml
parente5895f1749ea5e3dbad24341018333d101e53685 (diff)
downloadinstallation-guide-325e7229b079ce8367df7a7571aad8bfc8e1e5a9.zip
Remove all untranslated documents for Danish
Diffstat (limited to 'da/install-methods/tftp/bootp.xml')
-rw-r--r--da/install-methods/tftp/bootp.xml78
1 files changed, 0 insertions, 78 deletions
diff --git a/da/install-methods/tftp/bootp.xml b/da/install-methods/tftp/bootp.xml
deleted file mode 100644
index 1b0df1d95..000000000
--- a/da/install-methods/tftp/bootp.xml
+++ /dev/null
@@ -1,78 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 16879 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>
-
-</para><para>
-
-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 "ha" option, which specifies the
-hardware address of the client. The "bf" 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>