From owner-freebsd-doc@FreeBSD.ORG Thu Nov 28 23:46:40 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FBC8F67 for ; Thu, 28 Nov 2013 23:46:40 +0000 (UTC) Received: from gamma.ukrhub.net (gamma.ukrhub.net [94.125.120.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DB9E61BD1 for ; Thu, 28 Nov 2013 23:46:39 +0000 (UTC) Received: from gamma.ukrhub.net (localhost [127.0.0.1]) by gamma.ukrhub.net (8.14.7/8.14.7) with ESMTP id rASNkbTm051339; Fri, 29 Nov 2013 01:46:37 +0200 (EET) (envelope-from ds@ukrhub.net) Received: (from ds@localhost) by gamma.ukrhub.net (8.14.7/8.14.7/Submit) id rASNkaR2051338; Fri, 29 Nov 2013 01:46:36 +0200 (EET) (envelope-from ds@ukrhub.net) X-Authentication-Warning: gamma.ukrhub.net: ds set sender to ds@ukrhub.net using -f Date: Fri, 29 Nov 2013 01:46:36 +0200 From: Taras Korenko To: Warren Block Subject: Re: en/handbook/users: proposed corrections Message-ID: <20131128234636.GA50372@gamma.ukrhub.net> References: <20131126190644.GC25578@gamma.ukrhub.net> <20131128151032.GE52681@gamma.ukrhub.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Taras Korenko List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2013 23:46:40 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=koi8-u Content-Disposition: inline Updated version of the second patch follows. P.S.: the funniest thing is that contents of users chapter was integrated into basics chapter in r42953, users chapter was removed (again r42953), and reappeared after db5 merge, updated with new subchapter () still being excluded from the build. So, next, I am to adapt current two patches to the new location: basics chapter :-/ -- WBR, Taras Korenko --Dxnq1zWXvFF0Q93v Content-Type: text/x-diff; charset=koi8-u Content-Disposition: attachment; filename="03_2.en.hb.users.diff" Index: en_US.ISO8859-1/books/handbook/users/chapter.xml =================================================================== --- en_US.ISO8859-1/books/handbook/users/chapter.xml (revision 43259) +++ en_US.ISO8859-1/books/handbook/users/chapter.xml (working copy) @@ -984,7 +984,7 @@ There are several ways to do things as the superuser. The worst way is to log in as root directly. - Usually very little activity requires root + Very little activity requires superuser privileges, so logging off and logging in as root, performing tasks, then logging off and on again as a normal user is a waste of time. @@ -991,8 +991,8 @@ A better way is to use &man.su.1; without providing a login but using - to inherit the root environment. - Not providing a login will imply super user. For this to work - the login that must be in the wheel group. + Not providing a user name will imply superuser. For this to work + the current user must belong to the wheel group. An example of a typical software installation would involve the administrator unpacking the software as a normal user and then elevating their privileges for the build and installation of @@ -1014,12 +1014,12 @@ root is less painful than logging off and back on twice. - Using &man.su.1; works well for single systems or small + &man.su.1; works well for single systems or small networks with just one system administrator. For more complex - environments (or even for these simple environments) - sudo should be used. It is provided as a port, - security/sudo. It allows for - things like activity logging, granting users the ability to only + environments, + sudo is useful. It is available as a + security/sudo package or port. + sudo provides activity logging, granting users the ability to only run certain commands as the superuser, and several other options. --Dxnq1zWXvFF0Q93v--