* Reworded some sentence for consistency
* Mentioned /usr/home as a convention (/home is just mentioned) * Change some comma usage * Make use of <quote> tag instead of a literal "word"
This commit is contained in:
parent
71dc77b517
commit
2e0731b31b
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10608
1 changed files with 14 additions and 12 deletions
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.28 2001/08/22 05:37:50 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.29 2001/09/04 11:03:16 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="users">
|
||||
|
@ -22,7 +22,7 @@
|
|||
<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
|
||||
Obviously, only one of those users can be sitting in front of the screen and
|
||||
keyboard at any one time
|
||||
<footnote>
|
||||
<para>Well, unless you hook up multiple terminals, but we'll
|
||||
|
@ -114,7 +114,7 @@
|
|||
|
||||
<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
|
||||
the user to the system. Internally, FreeBSD uses the UID to
|
||||
identify users—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
|
||||
|
@ -166,7 +166,7 @@
|
|||
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
|
||||
time has elapsed the account cannot be used to log in to the
|
||||
system, although the account's directories and files will
|
||||
remain.</para>
|
||||
</listitem>
|
||||
|
@ -190,7 +190,8 @@
|
|||
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>.
|
||||
<filename>/home/<replaceable>username</replaceable></filename>
|
||||
or <filename>/usr/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>
|
||||
|
@ -243,8 +244,8 @@
|
|||
mean irreparable data loss.</para>
|
||||
|
||||
<para>So, the first thing you should do after reading this
|
||||
chapter, is to create an unprivileged user account for yourself
|
||||
for general usage, if you have not already. This applies equally
|
||||
chapter is to create an unprivileged user account for yourself
|
||||
for general usage if you have not already. This applies equally
|
||||
whether you are running a multi-user or single-user machine.
|
||||
Later in this chapter, we discuss how to create additional
|
||||
accounts, and how to change between the normal user and
|
||||
|
@ -379,7 +380,7 @@
|
|||
adding new users. It creates entries in the system
|
||||
<filename>passwd</filename> and <filename>group</filename>
|
||||
files. It will also create a home directory for the new user,
|
||||
copy in the default configuration files ("dotfiles") from
|
||||
copy in the default configuration files (<quote>dotfiles</quote>) from
|
||||
<filename>/usr/share/skel</filename>, and can optionally mail
|
||||
the new user a welcome message.</para>
|
||||
|
||||
|
@ -612,7 +613,7 @@ Other information:</screen>
|
|||
<command>ypchfn</command>, and
|
||||
<command>ypchsh</command>. NIS support is automatic, so
|
||||
specifying the <literal>yp</literal> before the command is
|
||||
not necessary. If this is confusing to you, don't worry, NIS will
|
||||
not necessary. If this is confusing to you, do not worry, NIS will
|
||||
be covered in <xref linkend="advanced-networking"></para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
@ -728,7 +729,7 @@ passwd: done</screen>
|
|||
pair, where <replaceable>name</replaceable> is a well-known
|
||||
identifier and <replaceable>value</replaceable> is an arbitrary
|
||||
string processed accordingly depending on the name. Setting up login
|
||||
classes and capabilities is rather straight-forward, and is also
|
||||
classes and capabilities is rather straight-forward and is also
|
||||
described in &man.login.conf.5;.</para>
|
||||
|
||||
<para>Resource limits are different from plain vanilla login
|
||||
|
@ -843,8 +844,9 @@ passwd: done</screen>
|
|||
<para>This is the maximum amount a memory a process may have
|
||||
requested to be locked into main memory (e.g., see
|
||||
&man.mlock.2;). Some system-critical programs, such as
|
||||
&man.amd.8;, do this so that their getting swapped out does not
|
||||
contribute to a system's thrashing in time of trouble.</para>
|
||||
&man.amd.8;, lock into main memory such that in the event
|
||||
of being swapped out, they do not contribute to
|
||||
a system's trashing in time of trouble.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
Loading…
Reference in a new issue