1 .\" Copyright (c) 1980, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)adduser.8 8.1 (Berkeley) 6/5/93
33 .\" $FreeBSD: src/share/man/man8/adding_user.8,v 1.3.2.3 2001/08/17 13:08:50 ru Exp $
34 .\" $DragonFly: src/share/man/man8/adding_user.8,v 1.4 2006/02/17 19:37:10 swildner Exp $
41 .Nd procedure for adding new users
43 A new user must choose a login name, which must not already appear in
46 .Pa /etc/mail/aliases .
47 It must also not begin with the hyphen
50 It is strongly recommended that it be all lower-case, and not contain
53 character, as that tends to confuse mailers.
54 An account can be added by editing a line into the passwd file; this
55 must be done with the password file locked e.g. by using
60 A new user is given a group and user id.
61 Login and user id's should be unique across the system, and often across
62 a group of systems, since they are used to control file access.
63 Typically, users working on similar projects will be put in the same groups.
64 At the University of California, Berkeley, we have groups for system staff,
65 faculty, graduate students, and special groups for large projects.
67 A skeletal account for a new user
71 ernie::25:30::0:0:Ernie Kovacs,508 Evans Hall,x7925,
72 642-8202:/a/users/ernie:/bin/csh
75 For a description of each of these fields, see
78 It is useful to give new users some help in getting started, supplying
79 them with a few skeletal files such as
91 contains skeletal definitions of such files.
92 New users should be given copies of these files which, for instance,
95 automatically at each login.
97 .Bl -tag -width /etc/master.passwdxx -compact
98 .It Pa /etc/master.passwd
100 .It Pa /usr/share/skel
101 skeletal login directory
115 procedure appeared in
118 User information should (and eventually will) be stored elsewhere.