From owner-freebsd-doc Mon Jun 4 17:10:11 2001 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DA41E37B405 for ; Mon, 4 Jun 2001 17:10:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.3/8.11.3) id f550A1p36452; Mon, 4 Jun 2001 17:10:01 -0700 (PDT) (envelope-from gnats) Received: from hall.mail.mindspring.net (hall.mail.mindspring.net [207.69.200.60]) by hub.freebsd.org (Postfix) with ESMTP id 03B3D37B401 for ; Mon, 4 Jun 2001 17:07:00 -0700 (PDT) (envelope-from vangyzen@core.vangyzen.net) Received: from hiro.vangyzen.net (user-2ivf85o.dialup.mindspring.com [165.247.160.184]) by hall.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id UAA00810 for ; Mon, 4 Jun 2001 20:06:56 -0400 (EDT) Received: (from vangyzen@localhost) by hiro.vangyzen.net (8.11.3/8.9.3) id f5508LS45713; Mon, 4 Jun 2001 20:08:21 -0400 (EDT) (envelope-from vangyzen) Message-Id: <200106050008.f5508LS45713@hiro.vangyzen.net> Date: Mon, 4 Jun 2001 20:08:21 -0400 (EDT) From: "Eric S. Van Gyzen" To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/27882: docs: Misspellings, Grammar Errors, Punctuation Errors Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 27882 >Category: docs >Synopsis: docs: Misspellings, Grammar Errors, Punctuation Errors >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 04 17:10:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Eric S. Van Gyzen >Release: FreeBSD 4.3-STABLE i386 >Organization: >Environment: System: FreeBSD hiro.vangyzen.net 4.3-STABLE FreeBSD 4.3-STABLE #0: Tue Apr 24 13:30:09 EDT 2001 vangyzen@hiro.vangyzen.net:/usr/src/sys/compile/HIRO i386 Modified File: $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.41 2001/05/28 13:41:56 sheldonh Exp $ >Description: See the following "diff" for a full description of the problems I fixed. Most were obvious typos. I am fairly certain that none of my fixes altered the semantics of the content. Incidentally, this is a pretty good introduction to NIS. Thanks! >How-To-Repeat: N/A >Fix: *** chapter.sgml.orig Mon Jun 4 19:36:12 2001 --- chapter.sgml Mon Jun 4 19:48:23 2001 *************** *** 1456,1462 **** master's data files. NIS slave servers provide the redundancy, which is needed in important environments. They also help to balance the load of the master server: NIS Clients always ! attach to the NIS server, whose response they get first, and this includes slave-server-replies. --- 1456,1462 ---- master's data files. NIS slave servers provide the redundancy, which is needed in important environments. They also help to balance the load of the master server: NIS Clients always ! attach to the NIS server whose response they get first, and this includes slave-server-replies. *************** *** 1552,1558 **** that it is part of. This is how multiple servers on one network can tell which server should answer which request. Think of the NIS domainname as the name for a group of hosts ! that are related in someway way. Some organizations choose to use their Internet domainname for their NIS domainname. This is not recommended as it can --- 1552,1558 ---- that it is part of. This is how multiple servers on one network can tell which server should answer which request. Think of the NIS domainname as the name for a group of hosts ! that are related in some way. Some organizations choose to use their Internet domainname for their NIS domainname. This is not recommended as it can *************** *** 1641,1647 **** ! Now, everything you have to do is to run the command /etc/netstart as superuser. It will setup everything for you, using the values you defined in /etc/rc.conf. --- 1641,1647 ---- ! Now, all you have to do is to run the command /etc/netstart as superuser. It will setup everything for you, using the values you defined in /etc/rc.conf. *************** *** 1815,1822 **** These two lines force the slave to sync its maps with the maps on the master server. Although this is not mandatory, because the master server ! tries to make sure any changes to it's NIS maps are ! communicated to it's slaves, the password information is so vital to systems that depend on the server, that it is a good idea to force the updates. This is more important on busy networks where map updates might not always --- 1815,1822 ---- These two lines force the slave to sync its maps with the maps on the master server. Although this is not mandatory, because the master server ! tries to make sure any changes to its NIS maps are ! communicated to its slaves, the password information is so vital to systems that depend on the server, that it is a good idea to force the updates. This is more important on busy networks where map updates might not always *************** *** 1857,1863 **** Setting up an NIS client Setting up a FreeBSD machine to be a NIS client is fairly ! straight forward. --- 1857,1863 ---- Setting up an NIS client Setting up a FreeBSD machine to be a NIS client is fairly ! straightforward. *************** *** 2044,2050 **** users and/or machines. On larger networks, you will forget to bar some users from logging onto sensitive machines, or you may even have to modify each ! machine separately, thus loosing the main benefit of NIS, centralized administration. The NIS developers' solution for this problem is called --- 2044,2050 ---- users and/or machines. On larger networks, you will forget to bar some users from logging onto sensitive machines, or you may even have to modify each ! machine separately, thus losing the main benefit of NIS, centralized administration. The NIS developers' solution for this problem is called *************** *** 2122,2128 **** ! pride, greed, envy, wraith, lust, sloth Less important servers. All members of the IT department are allowed to login onto these machines. --- 2122,2128 ---- ! pride, greed, envy, wrath, lust, sloth Less important servers. All members of the IT department are allowed to login onto these machines. *************** *** 2148,2161 **** -user line to each system's passwd for each user who is not allowed to login onto that system. If you forget just one entry, you could be in trouble. It may ! feasible to do this correctly during the initial setup, however you will eventually forget to add the lines for new users during day-to-day operations. After all, Murphy was an optimist. Handling this situation with netgroups offers several advantages. Each user need not be handled separately; ! you assign a user to one or netgroup and allow or forbid logins for all members of the netgroup. If you add a new machine, you will only have to define login restrictions for netgroups. If a new user is added, you will only have to add --- 2148,2161 ---- -user line to each system's passwd for each user who is not allowed to login onto that system. If you forget just one entry, you could be in trouble. It may ! be feasible to do this correctly during the initial setup, however you will eventually forget to add the lines for new users during day-to-day operations. After all, Murphy was an optimist. Handling this situation with netgroups offers several advantages. Each user need not be handled separately; ! you assign a user to one or more netgroups and allow or forbid logins for all members of the netgroup. If you add a new machine, you will only have to define login restrictions for netgroups. If a new user is added, you will only have to add *************** *** 2194,2200 **** The name of the host(s) where the following items are valid. If you do not specify a hostname, the entry is valid on all hosts. If you do specify a hostname, you ! will a realm of darkness, horror and utter confusion. --- 2194,2200 ---- The name of the host(s) where the following items are valid. If you do not specify a hostname, the entry is valid on all hosts. If you do specify a hostname, you ! will enter a realm of darkness, horror and utter confusion. *************** *** 2231,2237 **** BIGGRP1 (,joe1,domain) (,joe2,domain) (,joe3,domain) [...] BIGGRP2 (,joe16,domain) (,joe17,domain) [...] ! BIGGRP3 (,joe32,domain) (,joe33,domain) BIGGROUP BIGGRP1 BIGGRP2 BIGGRP3 You can repeat this process if you need more than 225 --- 2231,2237 ---- BIGGRP1 (,joe1,domain) (,joe2,domain) (,joe3,domain) [...] BIGGRP2 (,joe16,domain) (,joe17,domain) [...] ! BIGGRP3 (,joe31,domain) (,joe32,domain) BIGGROUP BIGGRP1 BIGGRP2 BIGGRP3 You can repeat this process if you need more than 225 *************** *** 2250,2256 **** netgroup, netgroup.byhost and netgroup.byuser. Use &man.ypcat.1; to ! check if your new NIS map are available: ellington&prompt.user; ypcat -k netgroup --- 2250,2256 ---- netgroup, netgroup.byhost and netgroup.byuser. Use &man.ypcat.1; to ! check if your new NIS maps are available: ellington&prompt.user; ypcat -k netgroup >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message