From owner-freebsd-doc@FreeBSD.ORG Tue Sep 30 21:17:52 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC2E916A4B3; Tue, 30 Sep 2003 21:17:52 -0700 (PDT) Received: from www.reppep.com (www.reppep.com [66.92.104.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41F9C43F93; Tue, 30 Sep 2003 21:17:51 -0700 (PDT) (envelope-from pepper@reppep.com) Received: from [66.92.104.201] (g4.reppep.com [66.92.104.201]) by www.reppep.com (Postfix) with ESMTP id A2C9BFE65; Wed, 1 Oct 2003 00:18:44 -0400 (EDT) Mime-Version: 1.0 X-Sender: pepper@mail.reppep.com Message-Id: In-Reply-To: <20030930180215.7438ba73.trhodes@FreeBSD.org> References: <20030930180215.7438ba73.trhodes@FreeBSD.org> Date: Wed, 1 Oct 2003 00:13:44 -0400 To: Tom Rhodes From: Chris Pepper Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: FreeBSD-doc@FreeBSD.org Subject: Re: Quick review requested X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2003 04:17:52 -0000 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. > > >+ >+ Configure Additional Network Services >+ >+ 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. 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. >+ -a /.amd_mnt -l syslog /host /etc/amd.map /net >/etc/amd.map >+ >+ The -a option specifies the default mount >+ location which is listed here as /.amd_mnt. s/location which is listed/location, which is specified/ >+ The -l option specifies the default >+ log file; however, when &man.syslogd.8; is >+ specified all log activity will be sent to the system log daemon. >+ The /host is used to mount an exported s/is used/argument is used/ >+ file system from a remote hostname, while s/hostname,/host,/ >+ /net is used to mount an exported file >+ system from an IP address. The >+ /etc/amd.map defines the default options s/defines/file defines/ >+ for AMD exports. >+ The is used to configure the system's s/is/option is/ >+ default MTA or mail server. Selecting this s/MTA or/MTA, "Mail Transport Agent, or/ (spell it out the first time, not later) >+ option will bring forth the following menu: s/forth/up/ >+ Selecting Sendmail will install >+ the popular Sendmail server which >+ is the &os; default. The option >+ will set Sendmail to be the default >+ MTA, but disables its ability to receive s/disables/disable/ >+ incoming email from the Internet. The other options here, >+ Postfix and >+ Exim act similar to s/Exim act/Exim, act/ >+ Sendmail, 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. s/selecting either of these is more of a user preference than anything else./some people prefer these alternatives to the Sendmail MTA. >+ The NFS client will >+ set the machine to work as a client for an >+ NFS server. An NFS server s/set the machine to work as a client for an NFS server./configures the system to communicate with a server via NFS. >+ 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 NFS 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/ >+ for more >+ information about client and server configuration. >+ Our next option is the >+ PCNFSD selection. This >+ option will install the >+ net/pcnfsd package from >+ the ports collection. This is a useful utility which provides >+ NFS authentication services for systems which >+ are unable to provide their own. For instance, Microsoft's s/their own. For instance,/their own, such as/ >+ DOS operating system. >+ The &man.rpcbind.8;, &man.rpc.statd.8;, and >+ &man.rpc.lockd.8; utilities are all used for Remote Procedure >+ Calls (RPC). The rpcbind.8 >+ utility handles the communication between NFS s/handles the communication/manages communication/ >+ servers, their clients, and is required for s/servers, their clients/servers and clients/ >+ NFS servers to operate correctly. The >+ rpc.statd daemon interacts with the >+ rpc.statd daemon on other hosts to provide >+ status monitoring. The reported status is usually held in the >+ /var/db/statd.status file. The final >+ option listed here is the rpc.lockd 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 rpc.statd 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 NFS servers and clients >+ to operate correctly. >+ >+ As we progress down the list the next item here is >+ , 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 >+ connectionless 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 Enter key. You will then be presented >+ with yet another menu, this time asking for the flags you wish >+ to be passed on to routed. The default is s/to be passed on to/to pass on/ >+ -q and it should already appear on the >+ screen. >+ >+ Next in line is the 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 rwhod >+ utility broadcasts system messages across the network >+ periodically, or collects them when in consumer >+ mode. This utility is great for monitoring the status of >+ machines on the network, but can be highly annoying when in >+ producer mode as it will broadcast messages >+ every three minutes or so. >+ >+ Next to the last option in the list we have the >+ &man.sshd.8; daemon. This is the secure shell server for >+ OpenSSH and it is highly recommended >+ over the standard telnet and >+ FTP servers. The sshd >+ server is used to create a secure connection from one host to >+ another by using encryption connections. s/another by using encryption connections/another using encrypted connections/ or /another using encrypted communications/ >+ Finally there is the TCP Extensions >+ option. This enables the TCP Extensions >+ as defined by RFC 1323 and s/as defined by/defined in/ (it doesn't enable all extensions) >+ RFC 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. 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: Rockefeller University: