DataMuseum.dk

Presents historical artifacts from the history of:

DKUUG/EUUG Conference tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about DKUUG/EUUG Conference tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download
Index: ┃ T a

⟦d98b2ca67⟧ TextFile

    Length: 2536 (0x9e8)
    Types: TextFile
    Names: »add-user.n«

Derivation

└─⟦a0efdde77⟧ Bits:30001252 EUUGD11 Tape, 1987 Spring Conference Helsinki
    └─ ⟦this⟧ »EUUGD11/euug-87hel/sec8/mcp/help/add-user.n« 

TextFile

.ce
.ul
add-user [ name ]
.sp
.ul
add-user
allows you to create a new account.  There are several stages to this
process.  If the optional
.ul
name
is supplied, mcp will use this as the user's login name, otherwise mcp will
create a login name from the user's real name using these steps:
.nf
.sp
.in +2
Trim real name of titles (e.g. Dr., Prof.)
Trim real name of suffixes (e.g. Jr., III)
Case-lower the entire real name.
If last name is not taken as a login name and it's less
    than eight characters in length, use it.
If real name has three initials, concatenate them.
If this is unused as a login, use it.
Truncate the last name to no more than 5 characters.
Append a '_'.
Append the first character of the first name.
If the result of the last two operations is already used
    as a login, increment the last character by one
    until a unique login is found.
.in -2
.sp
.fi
Mcp will then announce the result of all this to you.
.sp
Mcp will ask you (mostly) obvious questions about  this  new
account  until  it  has  enough  information  to  create it.
Default responses, if any, appear in brackets "[]".
.sp
When mcp prompts you with "Id: " it expects  a  string  that
would uniquely identify the owner of the account anywhere on
the planet.  Generally this would be a person's Social Security
Number.  The reason for requesting such identification
information is that mcp will use it to notify you if  you're
about  to create an account for a user that already has one.
You can specify "exception" here  if  you  don't  have  such
information;  this  is useful for non-human accounts such as
"ftp", and "uucp".
.sp
There is also more than one way to answer mcp's request for a password to
use.  You can specify "none" and the user won't have a password.  Specify
"unused" and the user will have asterisk placed in the password field of his
line in /etc/passwd.  This guarantees that this account has no valid
password and thus no one can log into this account and only the super-user
can su to it (since su doesn't ask the super-user for passwords).  This is
useful for non-human accounts such as "daemon" and "news".  If you specify
"generate", mcp will generate a good (and utterly random) password for the
user and tell you what it is.  Other than these special cases what you type
is what the password will be.  Be aware that mcp silently disallows control
characters and colons.
.sp
Remember, at any stage in the
.ul
add-user
process you can just hit the interrupt key and the command will
be aborted with no change.