From: Scott Schwartz schwartz@bio.cse.psu.edu
Subject: [9fans] Building a new Plan 9 system.
Date: Fri, 25 Sep 1998 23:36:03 -0400 [thread overview]
Message-ID: <19980926033603.kHCtf_f7MDkDzEeOT1xS5S0_Ow5tujiCqAyi4hhE7TM@z> (raw)
One thing on my at-home wishlist (if not todolist) is for the
fileserver to run enough user mode processes to also function as the
authentication server. Then you would only need two machines to get a
whole system, instead of three. Obviously, this is less of an issue
with a number of users.
next reply other threads:[~1998-09-26 3:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-26 3:36 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-10-05 13:59 G.David
1998-10-05 7:46 Nigel
1998-10-01 9:40 forsyth
1998-10-01 9:29 forsyth
1998-10-01 9:02 forsyth
1998-09-30 23:06 James
1998-09-26 10:00 forsyth
1998-09-26 9:39 forsyth
1998-09-26 3:43 Scott
1998-09-26 2:17 James
1998-09-25 8:59 miller
1998-09-25 6:04 James
1998-09-24 1:37 forsyth
1998-09-21 12:03 jmk
1998-09-21 8:24 Scott
1998-09-21 7:38 James
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=19980926033603.kHCtf_f7MDkDzEeOT1xS5S0_Ow5tujiCqAyi4hhE7TM@z \
--to=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).