Update the synopsis. Add information about the 'meta' information associated

with a Unix account (user name, password, GID, etc).

Spell Neil's name correctly.

en_US.ISO8859-1/books/handbook/users/chapter.sgml

@@ -1,14 +1,14 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.19 2001/07/23 22:51:33 chern Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.20 2001/07/30 17:18:54 murray Exp $
 -->
 
 <chapter id="users">
   <chapterinfo>
     <authorgroup>
       <author>
-        <firstname>Neils</firstname>
+        <firstname>Neil</firstname>
 	<surname>Blakey-Milner</surname>
 	<contrib>Contributed</contrib>
       </author>
@@ -21,11 +21,189 @@
   <sect1 id="users-synopsis">
     <title>Synopsis</title>
     
+    <para>FreeBSD allows multiple users to use the computer at the same time.
+      Obviously, only one of those users can be sat in front of the screen and
+      keyboard at any one time, but any number of users can log in through the
+      network to get their work done.  To use the system every user must have
+      an account.</para>
     
+    <para>After reading this chapter you will know:</para>
+
+    <itemizedlist>
+      <listitem>
+	<para>The differences between the various user accounts on a FreeBSD
+	  system</para>
+      </listitem>
+
+      <listitem>
+	<para>How to add user accounts</para>
+      </listitem>
+
+      <listitem>
+	<para>How to remove user accounts</para>
+      </listitem>
+
+      <listitem>
+	<para>How to change account details, such as the user's full name, or
+	preferred shell</para>
+      </listitem>
+
+      <listitem>
+	<para>How to set limits on a per-account basis, to control the
+	  resources such as memory and CPU time that accounts and groups of
+	  accounts are allowed to access</para>
+      </listitem>
+
+      <listitem>
+	<para>How to use groups to make account management easier</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>Before reading this chapter you should have read the
+      following:</para>
+
+    <itemizedlist>
+      <listitem>
+	<para>Unix Basics (<xref linkend="basics">)</para>
+      </listitem>
+    </itemizedlist>
+  </sect1>
+
+  <sect1 id="users-introduction">
+    <title>Introduction</title>
+
     <para>All access to the system is achieved via accounts, and all
       processes are run by users, so user and account management are
       of integral importance on FreeBSD systems.</para>
 
+    <para>Every account on a FreeBSD system has certain information associated
+      with it to identify the account.</para>
+
+    <variablelist>
+      <varlistentry>
+	<term>User name</term>
+
+	<listitem>
+	  <para>The user name as it would be typed at the
+	    <prompt>login:</prompt> prompt.  User names must be unique across
+	    the computer; you may not have two users with the same
+	    user name.  There are a number of rules for creating valid user
+	    names, documented in &man.passwd.5;; you would typically use user
+	    names that consist of eight or fewer all lower case
+	    characters.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>Password</term>
+
+	<listitem>
+	  <para>Each account has a password associated with it.  The password
+	    may be blank, in which case no password will be required to access
+	    the system.  This is normally a very bad idea; every account
+	    should have a password.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>User ID (UID)</term>
+
+	<listitem>
+	  <para>The UID is a number from 0 to 65536 used to uniquely identify
+	    the user to the system.  Internally FreeBSD uses the UID to
+	    identify users&mdash;any FreeBSD commands that allow you to
+	    specify a user name will convert it to the UID before working with
+	    it.  This means that you can have several accounts with different
+	    user names but the same UID.  As far as FreeBSD is concerned these
+	    accounts are one user.  It is unlikely you will ever need to do
+	    this.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>Group ID (GID)</term>
+
+	<listitem>
+	  <para>The GID is a number from 0 to 65536 used to uniquely identify
+	    the primary group that the user belongs to.  Groups are a
+	    mechanism for controlling access to resources based on a user's
+	    GID rather than their UID.  This can significantly reduce the size
+	    of some configuration files.  A user may also be in more than one
+	    group.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>Login class</term>
+
+	<listitem>
+	  <para>Login classes are an extension to the group mechanism that
+	    provide additional flexibility when tailoring the system to
+	    different users.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>Password change time</term>
+
+	<listitem>
+	  <para>By default FreeBSD does not force users to change their
+	    passwords periodically.  You can enforce this on a per-user basis,
+	    forcing some or all of your users to change their passwords after
+	    a certain amount of time has elapsed.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>Account expiry time</term>
+
+	<listitem>
+	  <para>By default FreeBSD does not expire accounts.  If you are
+	    creating accounts that you know have a limited lifespan, for
+	    example, in a school where you have accounts for the students,
+	    then you can specify when the account expires.  After the expiry
+	    time has elapsed the account can not be used to log in to the
+	    system, although the account's directories and files will
+	    remain.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>User's full name</term>
+
+	<listitem>
+	  <para>The user name uniquely identifies the account to FreeBSD, but
+	    does not necessarily reflect the user's real name.  This
+	    information can be associated with the account.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>Home directory</term>
+
+	<listitem>
+	  <para>The home directory is the full path to a directory on the
+	    system in which the user will start when logging on to the
+	    system.  A common convention is to put all user home directories
+	    under
+	    <filename>/home/<replaceable>username</replaceable></filename>.
+	    The user would store their personal files in their home directory,
+	    and any directories they may create in there.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term>User shell</term>
+
+	<listitem>
+	  <para>The shell provides the default environment users use to
+	    interact with the system.  There are many different kinds of
+	    shells, and experienced users will have their own preferences,
+	    which can be reflected in their account settings.</para>
+	</listitem>
+      </varlistentry>
+    </variablelist>
+
     <para>There are three main types of accounts; the <link
 	linkend="users-superuser">Superuser</link>, <link
 	linkend="users-system">system users</link>, and <link