diff options
| -rw-r--r-- | debian/changelog | 4 | ||||
| -rw-r--r-- | en/install-methods/tftp/bootp.xml | 5 |
2 files changed, 6 insertions, 3 deletions
diff --git a/debian/changelog b/debian/changelog index fb118dec3..62ab36c98 100644 --- a/debian/changelog +++ b/debian/changelog @@ -34,8 +34,10 @@ installation-guide (2009xxxx) UNRELEASED; urgency=low * Add links to website documenting braille keybindings. Thanks to Samuel Thibault for the patch. Closes: #534260. * Fix typo in chroot install appendix. Closes: #535494. + * Improve bootp documentation. Thanks to Holger Wansing for the patch. + Closes: #282614. - -- Frans Pop <fjp@debian.org> Mon, 06 Jul 2009 20:06:29 +0200 + -- Frans Pop <fjp@debian.org> Thu, 09 Jul 2009 15:19:54 +0200 installation-guide (20090427) unstable; urgency=low 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>. |