From: "rob pike, esq." <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Newbie question: groups
Date: Mon, 3 Mar 2003 20:46:14 -0800 [thread overview]
Message-ID: <f13ff6dc3217bf106beeb9ac44f1b277@mightycheese.com> (raw)
In-Reply-To: <808d37e3304c8e78a1b9446218d2997a@plan9.bell-labs.com>
> Actually we typically use the newuser command in fs(8)
> or the uname command in fossilcons(8), rather than
> edit /adm/users directly.
One important point is that the kernel knows nothing about this stuff.
If you wanted to provide an adminstrative interface to the file system
that doesn't involve typing on the console, go for it; it can all be done
in the file system itself.
-rob
next prev parent reply other threads:[~2003-03-04 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 22:00 Keith Nash
2003-03-03 22:23 ` Russ Cox
2003-03-04 4:46 ` rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 21:31 Keith Nash
2003-03-03 21:37 ` Russ Cox
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=f13ff6dc3217bf106beeb9ac44f1b277@mightycheese.com \
--to=rob@mightycheese.com \
--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).