svn commit: r43282 - in head/en_US.ISO8859-1/books/handbook: basics users
Taras Korenko
taras at FreeBSD.org
Fri Dec 6 13:43:50 UTC 2013
Author: taras
Date: Fri Dec 6 13:43:49 2013
New Revision: 43282
URL: http://svnweb.freebsd.org/changeset/doc/43282
Log:
This commit does the following:
+ some rewordings, simplifications and typo fixes in "Users and Basic
Account Management" section (discussed with wblock in ML [1]);
+ adds xml:ids to three examples and makes use of them;
+ nothing around "becoming superuser" -- that subchapter was rearranged
in r42873;
+ deletes suddenly revived handbook/users directory (the first attempt
was in r42953).
1. http://lists.freebsd.org/pipermail/freebsd-doc/2013-November/022881.html
Deleted:
head/en_US.ISO8859-1/books/handbook/users/
Modified:
head/en_US.ISO8859-1/books/handbook/basics/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/basics/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/basics/chapter.xml Fri Dec 6 13:13:19 2013 (r43281)
+++ head/en_US.ISO8859-1/books/handbook/basics/chapter.xml Fri Dec 6 13:43:49 2013 (r43282)
@@ -428,8 +428,8 @@ console none
<listitem>
<para>The user name is typed at the
- <prompt>login:</prompt> prompt. User names must be
- unique on the system as no two users can have the same
+ <prompt>login:</prompt> prompt. Each user must have
+ a unique
user name. There are a number of rules for creating
valid user names which are documented in
&man.passwd.5;. It is recommended to use user names
@@ -443,9 +443,7 @@ console none
<term>Password</term>
<listitem>
- <para>Each user account should have an associated
- password. While the password can be blank, this is
- highly discouraged.</para>
+ <para>Each account has an associated password.</para>
</listitem>
</varlistentry>
@@ -496,9 +494,8 @@ console none
<term>Password change time</term>
<listitem>
- <para>By default, &os; does not force users to change
- their passwords periodically. Password expiration can
- be enforced on a per-user basis using &man.pw.8;,
+ <para>By default, passwords do not expire. However,
+ password expiration can be enabled on a per-user basis,
forcing some or all users to change their passwords
after a certain amount of time has elapsed.</para>
</listitem>
@@ -586,7 +583,7 @@ console none
the superuser, since an extra space or missing character can
mean irreparable data loss.</para>
- <para>There are several ways to become gain superuser
+ <para>There are several ways to gain superuser
privilege. While one can log in as
<systemitem class="username">root</systemitem>, this is
highly discouraged.</para>
@@ -717,11 +714,12 @@ Password:
<filename>/usr/share/skel</filename>, and can optionally
mail the new user a welcome message. This utility must be
run as the
- <systemitem class="username">superuser</systemitem></para>
+ <systemitem class="username">superuser</systemitem>.</para>
<para>The &man.adduser.8; utility is interactive and walks
through the steps for creating a new user account. As seen
- in Example 4.2, either input the required information or
+ in <xref linkend="users-modifying-adduser"/>,
+ either input the required information or
press <keycap>Return</keycap> to accept the default value
shown in square brackets. In this example, the user has
been invited into the
@@ -730,7 +728,7 @@ Password:
access. When finished, the utility will prompt to either
create another user or to exit.</para>
- <example>
+ <example xml:id="users-modifying-adduser">
<title>Adding a User on &os;</title>
<screen>&prompt.root; <userinput>adduser</userinput>
@@ -868,7 +866,7 @@ Removing user (jru): mailspool home pass
<para>When passed no options, aside from an optional username,
&man.chpass.1; displays an editor containing user
- information. When the user exists from the editor, the user
+ information. When the user exits from the editor, the user
database is updated with the new information.</para>
<note>
@@ -877,15 +875,16 @@ Removing user (jru): mailspool home pass
superuser.</para>
</note>
- <para>In Example 4.4, the superuser has typed
+ <para>In <xref linkend="users-modifying-chpass-su"/>,
+ the superuser has typed
<command>chpass jru</command> and is now viewing the fields
that can be changed for this user. If
<systemitem class="username">jru</systemitem> runs this
command instead, only the last six fields will be displayed
- and available for editing. This is shown in Example
- 4.5.</para>
+ and available for editing. This is shown in
+ <xref linkend="users-modifying-chpass-ru"/>.</para>
- <example>
+ <example xml:id="users-modifying-chpass-su">
<title>Using <command>chpass</command> as
Superuser</title>
@@ -906,7 +905,7 @@ Home Phone:
Other information:</screen>
</example>
- <example>
+ <example xml:id="users-modifying-chpass-ru">
<title>Using <command>chpass</command> as Regular
User</title>
@@ -1165,8 +1164,8 @@ passwd: done</screen>
&man.sysctl.8;. Setting this limit too small may hinder
a user's productivity as it is often useful to be logged
in multiple times or to execute pipelines. Some tasks,
- such as compiling a large program, spawn multiple
- processes and other intermediate preprocessors.</para>
+ such as compiling a large program, start lots of
+ processes.</para>
</listitem>
</varlistentry>
@@ -1241,8 +1240,8 @@ passwd: done</screen>
<primary>limiting users</primary>
<secondary>sbsize</secondary>
</indexterm>,
- a user may consume in order to limit network
- communications.</para>
+ a user may consume. This can be generally used to limit
+ network communications.</para>
</listitem>
</varlistentry>
@@ -1395,7 +1394,7 @@ teamtwo:*:1100:jru,db</screen>
<para>In this example, the argument to <option>-m</option> is a
comma-delimited list of users who are to be added to the
group. Unlike the previous example, these users are appended
- to the group list and do not replace the list of existing
+ to the group and do not replace existing
users in the group.</para>
<example>
More information about the svn-doc-head
mailing list