Bug#282614: Patch for this bug
tags 282614 patch pending
thanks
Hi Holger,
On Thursday 09 July 2009, Holger Wansing wrote:
> Proposal patch attached.
Thanks a lot, but a few requests for the future.
* Please include *some* indication of what the bug is about or at least
that it affects the manual; I almost deleted your mail without looking
at the patch and that would probably have meant that it would have
disappeared in the BTS for a very long time (which would have been a
pity). Without opening the patch itself your mail contained *zero*
indication of what the patch is about...
* Please set the 'patch' tag for the BR when you submit patches.
* Please make the diff from either the manual directory or trunk root so
that the patch contains the full path to the file; that saves me having
to search where the modified file is.
I've applied your patch with two minor changes:
- added the <filename> tag for the config file
- fixed an unrelated other error so that the para makes a bit more sense
--- en/install-methods/tftp/bootp.xml (revision 59248)
+++ en/install-methods/tftp/bootp.xml (working copy)
@@ -61,10 +61,11 @@
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>.
Cheers,
FJP
Reply to: