diff options
author | Jeroen Schot <schot@a-eskwadraat.nl> | 2012-08-29 15:10:27 +0000 |
---|---|---|
committer | Jeroen Schot <schot@a-eskwadraat.nl> | 2012-08-29 15:10:27 +0000 |
commit | a292182f917a4104b223016e041410498f4d47a3 (patch) | |
tree | 31983bd3bb12e47ca30a949da0d472b93796a9ea /nl/install-methods/tftp/bootp.xml | |
parent | f842e23756734b3ce4932695707bc416810e46cc (diff) | |
download | installation-guide-a292182f917a4104b223016e041410498f4d47a3.zip |
Restart Dutch translation of D-I manual in PO format.
Diffstat (limited to 'nl/install-methods/tftp/bootp.xml')
-rw-r--r-- | nl/install-methods/tftp/bootp.xml | 73 |
1 files changed, 0 insertions, 73 deletions
diff --git a/nl/install-methods/tftp/bootp.xml b/nl/install-methods/tftp/bootp.xml deleted file mode 100644 index 86be45104..000000000 --- a/nl/install-methods/tftp/bootp.xml +++ /dev/null @@ -1,73 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 59293 untranslated --> - - - <sect2 condition="supports-bootp" id="tftp-bootp"> - <title>Setting up a BOOTP server</title> -<para> - -There are two BOOTP servers available for GNU/Linux. The first is CMU -<command>bootpd</command>. The other is actually a DHCP server: ISC -<command>dhcpd</command>. In &debian-gnu; these are contained in the -<classname>bootp</classname> and <classname>dhcp3-server</classname> -packages respectively. - -</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-gnu;, you can run <userinput>update-inetd --enable -bootps</userinput>, then <userinput>/etc/init.d/inetd -reload</userinput> to do so. Just in case your BOOTP server does not -run &debian;, 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 machines 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 in -<filename>/etc/dhcp3/dhcpd.conf</filename>, and restart -<command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server -restart</userinput>. - -</para> - </sect2> |