From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] adding a new user
Date: Thu, 26 Feb 2004 21:34:38 -0700 [thread overview]
Message-ID: <bf34c306985aaeaf4218396618787816@plan9.ucalgary.ca> (raw)
In-Reply-To: <20040227051716.GA23813@david.ath.cx>
the fossilcons man page contain all information about new users.
depending on installation you may need to create some extra
directories (apart from /usr/newuser, which fossil will create if you
don't tell it not to). on ucalgary i always forget to create
/mail/box/newuser and /cron/newuser so there's this script i use,
which has the potential to turn into a basic plan9 command if i write
the man page for it:
home% cat /bin/adduser
#!/bin/rc
rfork e
switch( $#*) {
case 1
newuser=$1
case *
{
echo 'usage: '^$0^' username'
exit usage
}
}
echo 'echo uname '^$newuser $newuser^' >> /srv/fscons'
echo 'echo create /active/mail/box/'^$user $user^' upas d775 >> /srv/fscons'
echo 'echo create /active/cron/'^$user $user $user^' d775 >> /srv/fscons'
home%
it works like 'kill' -- suggesting the command for creating a new
user. if there's anything extra i can edit the commands in place
before sending them to rc:
home% adduser f2f
echo uname f2f f2f >> /srv/fscons
echo create /active/mail/box/andrey andrey upas d775 >> /srv/fscons
echo create /active/cron/andrey andrey andrey d775 >> /srv/fscons
home%
works only as the fossilcons owner :)
andrey
next prev parent reply other threads:[~2004-02-27 4:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 5:17 David Caplan
2004-02-27 4:34 ` andrey mirtchovski [this message]
2004-02-27 10:17 ` [9fans] dvd decoding/playing Charles Forsyth
2004-02-27 10:29 ` Philippe Anel
2004-02-27 14:35 ` andrey mirtchovski
2014-12-02 16:33 [9fans] Adding a new user Mats Olsson
2014-12-02 16:42 ` Jacob Todd
2014-12-02 18:08 ` mischief
2014-12-02 20:54 ` Mats Olsson
2014-12-02 21:13 ` Mats Olsson
2014-12-02 17:10 sl
2014-12-02 21:08 sl
2014-12-03 0:37 ` erik quanstrom
2014-12-03 0:41 ` erik quanstrom
2014-12-03 8:31 ` Mats Olsson
2014-12-03 9:00 ` Mats Olsson
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=bf34c306985aaeaf4218396618787816@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
/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).