Return to adduser.8 CVS log

Up to [Research Unix] / researchv10dc / man / manb

Annotation of researchv10dc/man/manb/adduser.8, revision 1.1.1.1

1.1       root        1: .TH ADDUSER 8
                      2: .UC 4
                      3: .SH NAME
                      4: adduser \- procedure for adding new users
                      5: .SH DESCRIPTION
                      6: A new user must choose a login name, which must not already appear in
                      7: .I /etc/passwd.
                      8: An account can be added by editing a line into the passwd file; this must
                      9: be done with the password file locked e.g. by using
                     10: .IR vipw (8).
                     11: .PP
                     12: A new user is given a group and user id.
                     13: User id's should be distinct across a system, since they
                     14: are used to control access to files.
                     15: Typically, users working on
                     16: similar projects will be put in the same group.  Thus at UCB we have
                     17: groups for system staff, faculty, graduate students, and a few special
                     18: groups for large projects.  System staff is group \*(lq10\*(rq for historical
                     19: reasons, and the super-user is in this group.
                     20: .PP
                     21: A skeletal account for a new user \*(lqernie\*(rq would look like:
                     22: .IP
                     23: ernie::235:20:& Kovacs,508E,7925,6428202:/mnt/grad/ernie:/bin/csh
                     24: .PP
                     25: The first field is the login name \*(lqernie\*(rq.  The next field is the
                     26: encrypted password which is not given and must be initialized using
                     27: .IR passwd (1).
                     28: The next two fields are the user and group id's.
                     29: Traditionally, users in group 20 are graduate students and have account
                     30: names with numbers in the 200's.
                     31: The next field gives information about ernie's real name, office and office
                     32: phone and home phone.
                     33: This information is used by the
                     34: .IR finger (1)
                     35: program.
                     36: From this information we can tell that ernie's real name is
                     37: \*(lqErnie Kovacs\*(rq (the & here serves to repeat \*(lqernie\*(rq
                     38: with appropriate capitalization), that his office is 508 Evans Hall,
                     39: his extension is x2-7925, and this his home phone number is 642-8202.
                     40: You can modify the
                     41: .IR finger (1)
                     42: program if necessary to allow different information to be encoded in
                     43: this field.  The UCB version of finger knows several things particular
                     44: to Berkeley \- that phone extensions start \*(lq2\-\*(rq, that offices ending
                     45: in \*(lqE\*(rq are in Evans Hall and that offices ending in \*(lqC\*(rq are
                     46: in Cory Hall.
                     47: .PP
                     48: The final two fields give a login directory and a login shell name.
                     49: Traditionally, user files live on a file system which has the machines
                     50: single letter
                     51: .IR net (1)
                     52: address as the first of two characters.  Thus on the Berkeley CS Department
                     53: VAX, whose Berknet address is ``csvax'' abbreviated ``v'' the user file
                     54: systems are mounted on ``/va'', ``/vb'', etc.
                     55: On each such filesystem there are subdirectories there for each group
                     56: of users, i.e.: \*(lq/va/staff\*(rq and \*(lq/vb/prof\*(rq.
                     57: This is not strictly necessary but keeps the number of files in the
                     58: top level directories reasonably small.
                     59: .PP
                     60: The login shell will default to \*(lq/bin/sh\*(rq if none is given.
                     61: Most users at Berkeley choose \*(lq/bin/csh\*(rq so this is usually
                     62: specified here.
                     63: .PP
                     64: It is useful to give new users some help in getting started, supplying
                     65: them with a few skeletal files such as
                     66: .I \&.profile
                     67: if they use \*(lq/bin/sh\*(rq, or
                     68: .I \&.cshrc
                     69: and
                     70: .I \&.login
                     71: if they use \*(lq/bin/csh\*(rq.
                     72: The directory
                     73: \*(lq/usr/skel\*(rq contains skeletal definitions of such files.
                     74: New users should be given copies of these files which, for instance,
                     75: arrange to use
                     76: .IR tset (1)
                     77: automatically at each login.
                     78: .SH FILES
                     79: .ta 2i
                     80: /etc/passwd    password file
                     81: .br
                     82: /usr/skel      skeletal login directory
                     83: .SH SEE ALSO
                     84: passwd(1), finger(1), chsh(1), chfn(1), passwd(5), vipw(8)
                     85: .SH BUGS
                     86: User information should be stored in its own data base separate from
                     87: the password file.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.