From: Scott Schwartz schwartz@groucho.cse.psu.edu
Subject: sparc fileservers
Date: Mon, 1 Nov 1993 23:02:58 -0500 [thread overview]
Message-ID: <19931102040258.AU-tJ_n2EDyZ15cgjsIUqa0zJlgUGEvdaDJyhTe5peI@z> (raw)
| In fact, we have Plan 9 running here at UO using only the Unix
| based file server, since right now there are no spare machines
| to dedicate a Plan 9 file server.
That's more or less our situation as well. In a previous message you
said that you were running with hacked sources and lots of things
didn't work. I'm interested in hearing more about what you've done and
how things are working out these days.
next reply other threads:[~1993-11-02 4:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-11-02 4:02 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-11-03 7:28 mike
1993-11-02 4:32 David
1993-11-01 23:27 Mike
1993-11-01 22:56 Scott
1993-11-01 22:06 Dean
1993-11-01 19:36 Jim
1993-11-01 19:33 Arnold
1993-11-01 19:10 Scott
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=19931102040258.AU-tJ_n2EDyZ15cgjsIUqa0zJlgUGEvdaDJyhTe5peI@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).