diff options
| author | Frans Pop <elendil@planet.nl> | 2009-07-09 13:23:58 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2009-07-09 13:23:58 +0000 |
| commit | 2340037015313802ad68ad6d8c1fb4312b0a1b37 (patch) | |
| tree | 2fb50da989f0db800ac107651ebdcd2f4c34450a /en/install-methods/tftp/bootp.xml | |
| parent | a74273735e0459c82f04d89b5d5eb41d8ddc6717 (diff) | |
| download | installation-guide-2340037015313802ad68ad6d8c1fb4312b0a1b37.zip | |
Improve bootp documentation
Thanks to Holger Wansing for the patch.
Diffstat (limited to 'en/install-methods/tftp/bootp.xml')
| -rw-r--r-- | en/install-methods/tftp/bootp.xml | 5 |
1 files changed, 3 insertions, 2 deletions
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>. |