9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sergey Zhilkin <szhilkin@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Adding a new user on 9-Front
Date: Mon, 23 Dec 2013 09:19:45 +0400	[thread overview]
Message-ID: <CAOFTvPLxYeJ1wrxizz5Y4GKHxFyQ_XNvOcECqOcqHkermsXbKw@mail.gmail.com> (raw)
In-Reply-To: <CABwHSOvwy1kBFb8=BbKvF4od7HAR6c8N3OJUsFcfmDp-d2YAiQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]

Hello !
>From - https://code.google.com/p/plan9front/wiki/admin
Adding Users

Add a new user on the file server:

echo newuser username >>/srv/cwfs.cmd

If needed, make the new user a member of the upas (email) group:

echo newuser upas +username >>/srv/cwfs.cmd

The newuser filesystem command is described in the
fs(8)<http://man.aiju.de/8/fs> manpage.
Examine the '/adm/users' file to investigate the results.

To add a new user to the auth server, make sure auth/keyfs is running, then
set an auth password for the user:

auth/changeuser username

New users are created without a profile, mail directory, tmp directory
(needed to edit files with sam) or other confections. To install a default
profile for a new user, upon first login, run:

. /sys/lib/newuser

then edit /usr/username/lib/profile to your own specifications.

See cwfs(4) <http://man.aiju.de/4/cwfs> and fs(8) <http://man.aiju.de/8/fs>
 and auth(8) <http://man.aiju.de/8/auth>.




2013/12/23 Blake McBride <blake@mcbride.name>

> Greetings,
>
> I've searched the net to find a way to add a new user.  The following
> command doesn't work:
>
> con -l /srv/fscons
>
> I gather that command is for fossil, and fossil isn't used anymore.  I
> poked around /srv but couldn't find a substitute.  Appreciate any help.
>
> Blake
>
>


-- 
С наилучшими пожеланиями
Жилкин Сергей
With best regards
Zhilkin Sergey

[-- Attachment #2: Type: text/html, Size: 6176 bytes --]

  reply	other threads:[~2013-12-23  5:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23  2:37 Blake McBride
2013-12-23  5:19 ` Sergey Zhilkin [this message]
2013-12-23  6:15   ` Matthew Veety
2013-12-23 13:34     ` erik quanstrom
2013-12-23 13:46       ` Richard Miller
2013-12-23 13:55         ` erik quanstrom
2013-12-23 14:36   ` Blake McBride
2013-12-23 15:10   ` Blake McBride
2013-12-23 15:32     ` Bence Fábián
2013-12-23 17:13       ` sl
2013-12-23 18:00       ` Blake McBride
2013-12-23 18:03         ` Blake McBride
2013-12-23 18:28           ` Kurt H Maier
2013-12-23 20:03             ` Blake McBride
2013-12-23 20:18               ` erik quanstrom
2013-12-23 20:23               ` Rubén Berenguel
2013-12-23 20:48                 ` Blake McBride
2013-12-23 21:20                   ` Steve Simon
2013-12-23 20:51               ` Kurt H Maier
2013-12-23 21:45                 ` Blake McBride
2013-12-23 22:00                   ` Matthew Veety
2013-12-23 22:07                   ` sl
2013-12-23 22:45                     ` erik quanstrom
2013-12-23 23:47                       ` sl
2013-12-23 23:54                       ` Kurt H Maier
2013-12-24 12:06                         ` Steffen Daode Nurpmeso
2013-12-24 12:24                           ` lucio
2013-12-24 17:47                             ` Steffen Daode Nurpmeso
2013-12-25  5:30                               ` lucio
2013-12-25  5:58                         ` Federico G. Benavento
2013-12-24  0:16                   ` Kurt H Maier
2013-12-24  0:57                     ` andrey mirtchovski
2013-12-24  2:49                       ` Skip Tavakkolian
2013-12-24  3:03                         ` Bruce Ellis
2013-12-23 19:18           ` Richard Miller
2013-12-23 19:30             ` cinap_lenrek
2013-12-23 19:37               ` erik quanstrom
2013-12-23 20:29                 ` cinap_lenrek
2013-12-23 15:42     ` cinap_lenrek
2013-12-23  9:38 ` Richard Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOFTvPLxYeJ1wrxizz5Y4GKHxFyQ_XNvOcECqOcqHkermsXbKw@mail.gmail.com \
    --to=szhilkin@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).