Date: Wed, 1 Oct 2003 00:13:44 -0400 From: Chris Pepper <pepper@reppep.com> To: Tom Rhodes <trhodes@FreeBSD.org> Cc: FreeBSD-doc@FreeBSD.org Subject: Re: Quick review requested Message-ID: <p06100302bb9ffc71a931@[66.92.104.201]> In-Reply-To: <20030930180215.7438ba73.trhodes@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
At 6:02 PM -0400 2003/09/30, Tom Rhodes wrote: Tom, As someone who went through the options tonight, I found this very helpful. I have lots of niggles, though... >--- doc.old/en_US.ISO8859-1/books/handbook/install/chapter.sgml > Mon Sep 29 13:40:57 2003 >+++ doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml Mon >Sep 29 18:39:26 2003 >@@ -3382,6 +3382,233 @@ > post-installation configuration.</para> > </sect2> > >+ <sect2 id="network-services"> >+ <title>Configure Additional Network Services</title> >+ >+ <para>Configuring the network services can be a daunting s/the network/network/ (any network services; not a canonical set) >+ task for new users if they lack any previous network >configuration knowledge. s/lack any previous/lack previous/ (people might have some, but still be intimidated) >+ Configuring a network >+ is an important aspect of &os;, therefore users should at least >+ have an understanding of various services available to them.</para> Nah, networking is an important aspect of FreeBSD; configuring a network is an important aspect of managing a FBSD system. I actually think "have an understanding of various services" is too ambitious -- most users don't know about most of the network ports that are available. How about: Networking (including the Internet) is critical to all modern operating systems, including &os;; as a result, it's very useful to have some understanding &os;'s extensive networking capabilities. >+ <screen>-a /.amd_mnt -l syslog /host /etc/amd.map /net >/etc/amd.map</screen> >+ >+ <para>The <literal>-a</literal> option specifies the default mount >+ location which is listed here as <filename>/.amd_mnt</filename>. s/location which is listed/location, which is specified/ >+ The <literal>-l</literal> option specifies the default >+ <filename>log</filename> file; however, when &man.syslogd.8; is >+ specified all log activity will be sent to the system log daemon. >+ The <filename>/host</filename> is used to mount an exported s/is used/argument is used/ >+ file system from a remote hostname, while s/hostname,/host,/ >+ <filename>/net</filename> is used to mount an exported file >+ system from an <acronym>IP</acronym> address. The >+ <filename>/etc/amd.map</filename> defines the default options s/defines/file defines/ >+ for <acronym>AMD</acronym> exports.</para> >+ <para>The <option>Mail</option> is used to configure the system's s/is/option is/ >+ default <acronym>MTA</acronym> or mail server. Selecting this s/<acronym>MTA</acronym> or/<acronym>MTA</acronym>, "Mail Transport Agent, or/ (spell it out the first time, not later) >+ option will bring forth the following menu:</para> s/forth/up/ >+ <para>Selecting <application>Sendmail</application> will install >+ the popular <application>Sendmail</application> server which >+ is the &os; default. The <option>Sendmail local</option> option >+ will set <application>Sendmail</application> to be the default >+ <acronym>MTA</acronym>, but disables its ability to receive s/disables/disable/ >+ incoming email from the Internet. The other options here, >+ <application>Postfix</application> and >+ <application>Exim</application> act similar to s/<application>Exim</application> act/<application>Exim</application>, act/ >+ <application>Sendmail</application>, as in they both deliver s/as in/in that/ >+ email; however, selecting either of these is more of a user >+ preference than anything else.</para> s/selecting either of these is more of a user preference than anything else./some people prefer these alternatives to the Sendmail MTA. >+ <para>The <acronym>NFS</acronym> client will >+ set the machine to work as a client for an >+ <acronym>NFS</acronym> server. An <acronym>NFS</acronym> server s/set the machine to work as a client for an <acronym>NFS</acronym> server./configures the system to communicate with a server via <acronym>NFS</acronym>. >+ exports remotely mounted file systems to other machines on the local s/exports remotely mounted file systems/makes file systems available/ s/local// >+ network via the <acronym>NFS</acronym> protocol. If this is >+ a stand alone machine, this option can remain unselected. The >+ system may require more configuration later, see s/later, see/later; see/ >+ <xref linkend="network-nfs"> for more >+ information about client and server configuration.</para> >+ <para>Our next option is the >+ <acronym>PCNFSD</acronym> selection. This >+ option will install the >+ <filename role="package">net/pcnfsd</filename> package from >+ the ports collection. This is a useful utility which provides >+ <acronym>NFS</acronym> authentication services for systems which >+ are unable to provide their own. For instance, Microsoft's s/their own. For instance,/their own, such as/ >+ <acronym>DOS</acronym> operating system.</para> >+ <para>The &man.rpcbind.8;, &man.rpc.statd.8;, and >+ &man.rpc.lockd.8; utilities are all used for Remote Procedure >+ Calls (<acronym>RPC</acronym>). The <command>rpcbind.8</command> >+ utility handles the communication between <acronym>NFS</acronym> s/handles the communication/manages communication/ >+ servers, their clients, and is required for s/servers, their clients/servers and clients/ >+ <acronym>NFS</acronym> servers to operate correctly. The >+ <command>rpc.statd</command> daemon interacts with the >+ <command>rpc.statd</command> daemon on other hosts to provide >+ status monitoring. The reported status is usually held in the >+ <filename>/var/db/statd.status</filename> file. The final >+ option listed here is the <command>rpc.lockd</command> option, >+ which, when selected, will provide for file locking. This is s/will provide for for file locking./provides file locking services./ >+ usually used with <command>rpc.statd</command> to monitor what >+ hosts are requesting locks and how frequent they request them. /frequent/frequently/ >+ While these last two options are marvelous for debugging, they >+ are not required for <acronym>NFS</acronym> servers and clients >+ to operate correctly.</para> >+ >+ <para>As we progress down the list the next item here is >+ <option>Routd</option>, which is the route daemon. The s/Routd/Routed/ s/route daemon./routing daemon./ >+ &man.routed.8; utility manages the network routing tables, s/the network/network/ (other programs may manage such tables separately) >+ discovers multicast routers, and supplies a copy of the routing >+ tables to any physically connected host on the network upon >+ request. This is mainly used for routing >+ <quote>connectionless</quote> protocols (see &man.icmp.4 and >+ &man.udp.4;). When selected, a menu will be presented >+ requesting the default location of the utility. The default >+ location is already defined for you and can be selected with >+ the <keycap>Enter</keycap> key. You will then be presented >+ with yet another menu, this time asking for the flags you wish >+ to be passed on to <command>routed</command>. The default is s/to be passed on to/to pass on/ >+ <literal>-q</literal> and it should already appear on the >+ screen.</para> >+ >+ <para>Next in line is the <option>Rwhod</option> option which, >+ when selected, will have the &man.rwhod.8; daemon start up s/will have the &man.rwhod.8; daemon start up/will start the &man.rwhod.8; daemon/ >+ during system initialization. The <command>rwhod</command> >+ utility broadcasts system messages across the network >+ periodically, or collects them when in <quote>consumer</quote> >+ mode. This utility is great for monitoring the status of >+ machines on the network, but can be highly annoying when in >+ <quote>producer mode</quote> as it will broadcast messages >+ every three minutes or so.</para> >+ >+ <para>Next to the last option in the list we have the >+ &man.sshd.8; daemon. This is the secure shell server for >+ <application>OpenSSH</application> and it is highly recommended >+ over the standard <command>telnet</command> and >+ <acronym>FTP</acronym> servers. The <command>sshd</command> >+ server is used to create a secure connection from one host to >+ another by using encryption connections.</para> s/another by using encryption connections/another using encrypted connections/ or /another using encrypted communications/ >+ <para>Finally there is the <acronym>TCP</acronym> Extensions >+ option. This enables the <acronym>TCP</acronym> Extensions >+ as defined by <acronym>RFC</acronym> 1323 and s/as defined by/defined in/ (it doesn't enable all extensions) >+ <acronym>RFC</acronym> 1644. While on many hosts this can >+ speed up connections, but can also cause some connections to s/but can/it can/ >+ or be dropped. It is not recommended for servers but may be >+ beneficial for stand alone machines.</para> It's the default in my 4.9-rc1 install running now; should it be turned off? Where is more info on the implications available? Chris Pepper -- Chris Pepper: <http://www.reppep.com/~pepper/>; Rockefeller University: <http://www.rockefeller.edu/>;home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06100302bb9ffc71a931>