From: Steinar Knutsen sk@nvg.unit.no
Subject: Running Plan 9 on NeXT with u9fs
Date: Tue, 3 Oct 1995 11:55:15 -0400 [thread overview]
Message-ID: <19951003155515.hlNG9dMyB9gXKbEs6XgRboJlq3QFTNJcXVGdZ6LebCs@z> (raw)
I would be very much interested in hearing about your experiences when setting
up a NeXT u9fs. (As an answer to your offer on writing a summary aabout this
if it was enough interest...)
--
Steinar Knutsen sk@nvg.unit.no Finger for PGP public key.
"When people talk about space as a hostile enviroment, they are thinking
the wrong way. They are thinking about coming home." -Story Musgrave
next reply other threads:[~1995-10-03 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-03 15:55 Steinar [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-10-03 19:33 Ta-Wei
1995-10-03 3:04 Ta-Wei
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=19951003155515.hlNG9dMyB9gXKbEs6XgRboJlq3QFTNJcXVGdZ6LebCs@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).