Date: Tue, 27 Nov 2001 05:50:09 -0800 (PST) From: setantae <setantae@submonkey.net> To: freebsd-doc@freebsd.org Subject: Re: docs/32229: Omission from Handbook Chapter 17.8 (DHCP) Message-ID: <200111271350.fARDo9702039@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR docs/32229; it has been noted by GNATS. From: setantae <setantae@submonkey.net> To: Giorgos Keramidas <charon@labs.gr> Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: docs/32229: Omission from Handbook Chapter 17.8 (DHCP) Date: Tue, 27 Nov 2001 13:43:40 +0000 On Tue, Nov 27, 2001 at 05:49:27AM +0200, Giorgos Keramidas wrote: > 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. nsgmls complained about it being missing, so I added it. Same story with the </co> bits in the programlisting. If it isn't necessary that's great, as I won't have to worry about it in the future :) > > <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> Noted. > > <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. They both suit me. That's the bit that I nicked from the DHCP client chapter! > 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. OK, noted. > > <callout arearefs="domain-name-servers"> > > <para>This option specifies a comma seperated list of DNS > > comma separated ? Whoops. > 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. It is, yes. > > 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 :-) Yeah, I was worried about that, but since this is my first effort at docbook, had no idea how to deal with referring to manpages that aren't in the base system. > 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 :-) Thanks very much. It's not discouraging at all; I don't really know what I'm doing and need the guidance! Ceri 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?200111271350.fARDo9702039>