Proposal patch attached.
Holger
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 2.5.0
under DEBIAN GNU/LINUX 5.0.0 - L e n n y
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
--- bootp.xml 2009-01-14 22:13:14.000000000 +0100
+++ bootp_workingcopy.xml 2009-07-09 14:22:50.000000000 +0200
@@ -64,7 +64,7 @@
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
+block for the subnet containing the client in /etc/dhcp3/dhcpd.conf, and restart
<command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server
restart</userinput>.
