From: "Steve Simon" <steve@quintile.net>
To: corey@bitworthy.net, 9fans@9fans.net
Subject: Re: [9fans] fscons users -r/-w <file> vs. editing /adm/users manually
Date: Sun, 16 May 2010 09:55:36 +0100 [thread overview]
Message-ID: <1232d69cdfa6b088e869c0793d2f6ca7@quintile.net> (raw)
In-Reply-To: <201005151816.22124.corey@bitworthy.net>
re: when users leave
I think the labs policy was to change the name of the user from
frank:frank
to
was-frank:frank
the first name is what is used by auth and is reported by dirstat()
the seccond name is what is held on the disk (ken fs uses integers here).
Beware: this is from memory, I have not tested this.
-Steve
next prev parent reply other threads:[~2010-05-16 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 0:55 erik quanstrom
2010-05-16 1:16 ` Corey
2010-05-16 1:28 ` erik quanstrom
2010-05-16 2:34 ` Corey
2010-05-16 8:55 ` Steve Simon [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-15 23:56 Corey
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=1232d69cdfa6b088e869c0793d2f6ca7@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
--cc=corey@bitworthy.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).