Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Nov 2013 17:10:32 +0200
From:      Taras Korenko <ds@ukrhub.net>
To:        Warren Block <wblock@wonkity.com>
Cc:        freebsd-doc@freebsd.org
Subject:   Re: en/handbook/users: proposed corrections
Message-ID:  <20131128151032.GE52681@gamma.ukrhub.net>
In-Reply-To: <alpine.BSF.2.00.1311270927350.64907@wonkity.com>
References:  <20131126190644.GC25578@gamma.ukrhub.net> <alpine.BSF.2.00.1311270927350.64907@wonkity.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--IiVenqGWf+H9Y6IX
Content-Type: text/plain; charset=koi8-u
Content-Disposition: inline

  ... and the last (previously unnoticed) chunk follows:

-- 
  WBR, Taras Korenko

--IiVenqGWf+H9Y6IX
Content-Type: text/x-diff; charset=koi8-u
Content-Disposition: attachment; filename="02_1.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 @@
 
     <para>There are several ways to do things as the superuser.  The
       worst way is to log in as <systemitem class="username">root</systemitem> directly.
-      Usually very little activity requires <systemitem class="username">root</systemitem>
+      Usually very little activity requires superuser privileges,
       so logging off and logging in as <systemitem class="username">root</systemitem>,
       performing tasks, then logging off and on again as a normal user
       is a waste of time.</para>
@@ -991,8 +991,8 @@
 
     <para>A better way is to use &man.su.1; without providing a login
       but using <literal>-</literal> to inherit the root environment.
-      Not providing a login will imply super user.  For this to work
-      the login that must be in the <systemitem class="groupname">wheel</systemitem> group.
+      Not providing a login will imply superuser.  For this to work
+      the current user must belong to the <systemitem class="groupname">wheel</systemitem> 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
@@ -1016,10 +1016,10 @@
 
     <para>Using &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)
-      <command>sudo</command> should be used.  It is provided as a port,
-      <package>security/sudo</package>.  It allows for
-      things like activity logging, granting users the ability to only
+      environments
+      <command>sudo</command> might be used.  It is available as a
+      <package>security/sudo</package> package or port.
+      <command>sudo</command> provides activity logging, granting users the ability to only
       run certain commands as the superuser, and several other
       options.</para>
   </sect1>

--IiVenqGWf+H9Y6IX--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131128151032.GE52681>