diff options
Diffstat (limited to 'en/install-methods/tftp/bootp.xml')
| -rw-r--r-- | en/install-methods/tftp/bootp.xml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/en/install-methods/tftp/bootp.xml b/en/install-methods/tftp/bootp.xml index cda0f9c66..f0b0eab42 100644 --- a/en/install-methods/tftp/bootp.xml +++ b/en/install-methods/tftp/bootp.xml @@ -3,14 +3,14 @@ <sect2 condition="supports-bootp" id="tftp-bootp"> - <title>Setting up BOOTP server</title> + <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; these are contained in the -<classname>bootp</classname> and <classname>dhcp</classname> packages -respectively. +<classname>bootp</classname> and <classname>dhcp3-server</classname> +packages respectively. </para><para> @@ -61,11 +61,11 @@ 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 +those, read the section <xref linkend="dhcpd"/>. In that case, 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 +<command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>. </para> |