Date: Fri, 13 Dec 2013 09:05:40 +0000 (UTC) From: Taras Korenko <taras@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43328 - head/en_US.ISO8859-1/books/handbook/basics Message-ID: <201312130905.rBD95epa045260@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: taras Date: Fri Dec 13 09:05:40 2013 New Revision: 43328 URL: http://svnweb.freebsd.org/changeset/doc/43328 Log: Whitespace-only fixes (covering two previos commits), translators please ignore. 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 13 08:29:32 2013 (r43327) +++ head/en_US.ISO8859-1/books/handbook/basics/chapter.xml Fri Dec 13 09:05:40 2013 (r43328) @@ -429,9 +429,8 @@ console none <listitem> <para>The user name is typed at the <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 + 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 that consist of eight or fewer, all lower case characters in order to maintain backwards @@ -495,9 +494,10 @@ console none <listitem> <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> + 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> </varlistentry> @@ -583,8 +583,8 @@ console none the superuser, since an extra space or missing character can mean irreparable data loss.</para> - <para>There are several ways to gain superuser - privilege. While one can log in as + <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> @@ -637,11 +637,12 @@ Password: <para>&os; provides a variety of different commands to manage user accounts. The most common commands are summarized in - <xref linkend="users-modifying-utilities"/>, followed by some examples of their usage. See - the manual page for each utility for more details and usage - examples.</para> + <xref linkend="users-modifying-utilities"/>, followed by some + examples of their usage. See the manual page for each utility + for more details and usage examples.</para> - <table frame="none" pgwide="1" xml:id="users-modifying-utilities"> + <table frame="none" pgwide="1" + xml:id="users-modifying-utilities"> <title>Utilities for Managing User Accounts</title> <tgroup cols="2"> @@ -713,16 +714,14 @@ Password: configuration files from <filename>/usr/share/skel</filename>, and can optionally mail the new user a welcome message. This utility must be - run as the - superuser.</para> + run as the superuser.</para> <para>The &man.adduser.8; utility is interactive and walks through the steps for creating a new user account. As seen - 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 + 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 <systemitem class="groupname">wheel</systemitem> group, allowing them to become the superuser with &man.su.1;. When finished, the utility will prompt to either @@ -875,11 +874,10 @@ Removing user (jru): mailspool home pass superuser.</para> </note> - <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 + <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 <xref linkend="users-modifying-chpass-ru"/>.</para> @@ -1394,8 +1392,8 @@ 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 and do not replace existing - users in the group.</para> + to the group and do not replace existing users in the + group.</para> <example> <title>Using &man.id.1; to Determine Group Membership</title>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201312130905.rBD95epa045260>