From 2340037015313802ad68ad6d8c1fb4312b0a1b37 Mon Sep 17 00:00:00 2001
From: Frans Pop <elendil@planet.nl>
Date: Thu, 9 Jul 2009 13:23:58 +0000
Subject: Improve bootp documentation

Thanks to Holger Wansing for the patch.
---
 en/install-methods/tftp/bootp.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'en/install-methods/tftp/bootp.xml')

diff --git a/en/install-methods/tftp/bootp.xml b/en/install-methods/tftp/bootp.xml
index f0b0eab42..b083ba03e 100644
--- a/en/install-methods/tftp/bootp.xml
+++ b/en/install-methods/tftp/bootp.xml
@@ -61,10 +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"/>.  In that case, you
+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
+block for the subnet containing the client in
+<filename>/etc/dhcp3/dhcpd.conf</filename>, and restart
 <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server
 restart</userinput>.
 
-- 
cgit v1.2.3