Date: Tue, 27 Nov 2001 05:49:27 +0200 From: Giorgos Keramidas <charon@labs.gr> To: setantae <setantae@submonkey.net> Cc: freebsd-doc@FreeBSD.ORG Subject: Re: docs/32229: Omission from Handbook Chapter 17.8 (DHCP) Message-ID: <20011127034927.GA2663@hades.hell.gr> In-Reply-To: <200111261900.fAQJ03809531@freefall.freebsd.org> References: <200111261900.fAQJ03809531@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2001-11-26 11:00:03, setantae wrote: > > <para>The server portion of the suite is not provided as part of > FreeBSD, and so you will need to install the <port>net/isc-dhcp2</port> > port to provide this service. See <xref linkend="ports"></xref> for more </xref> is not really necessary, I think. > <para>Also included with this reply is a length of time for which > this information can be used by that particular client. This is > known as a DHCP "lease" and a new lease must be acquired by the <quote>lease</quote> > configuration file, and rebuild the kernel. For more > information about building kernels, see <xref > linkend="kernelconfig"></xref>.</para> </xref> again... > <para>The <devicename>bpf</devicename> device is already > part of the <filename>GENERIC</filename> kernel that is > supplied with FreeBSD, so if you do not have a custom > kernel, you should not need to create one in order to get > DHCP working.</para> I'd prefer this without the double negative. Something like: ...so, even if you are running the GENERIC kernel, you will not need to build a custom kernel to get DHCP working.</para> > <note> > <para>For those who are particularly security conscious, > you should be warned that <devicename>bpf</devicename> "Those of you who are particularly security consious, should bear in mind that..." looks a bit better here. But this might be just me being wrong. > <programlisting> > option domain-name "example.com";<co id="domain-name"></co> > option domain-name-servers 192.168.4.100;<co id="domain-name-servers"></co> ... > } > </programlisting> I tend to prefer <programlisting> tags written with the first and last lines having no whitespace/newline characters, as in: <programlisting>Text here... more text end of text</programlisting> but this and other whitespace changes are easy to make before committing this. > <callout arearefs="domain-name-servers"> > <para>This option specifies a comma seperated list of DNS comma separated ? > <screen> > &prompt.root; <userinput>/usr/local/etc/rc.d/isc-dhcpd.sh start</userinput> > </screen> The same as <programlisting> here. It's better when written as: <screen>command...</screen> Perhaps a paragraph needs to be added to note that the script should be made executable. I'm not sure if it will be made executable by the installation. Something similar to: <para>The startup script for the DHCP daemon is installed by the <port>net/isc-dhcp2</port> as <filename>/usr/local/etc/rc.d/isc-dhcpd.sh</filename>. If this script is executable, then the DHCP daemon will automatically be started at boot time. Use &man.chmod.1; to make it executable if it isn't.</para> <screen>&prompt.root; <userinput>chmod +x /usr/local/etc/rc.d/isc-dhcpd.sh</userinput></screen> > resides in <filename>/usr/local/sbin</filename>. The &man.dhcpd.8; My entities do not include a &man.dhcp.8; entry. Perhaps one should be added, even though this is a program installed from the ports? :-/ > another DHCP server on a separate network. The &man.dhcrelay.8; Similarly for this entity :-) I hope I'm not being too anal-retentive and this discourages you from submitting more stuff like this work. This looks absolutely marvellous already :-) Let's wait to see if anyone else has comments on this, for a while, and then I think it should be committed more or less verbatim. CVS makes changes very easy to do in the future anyways, if they're needed. -giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011127034927.GA2663>