From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu server/terminal combination
Date: Thu, 30 May 2002 14:24:31 -0400 [thread overview]
Message-ID: <0b99cba020d43dae0c771e8a591f7c88@plan9.bell-labs.com> (raw)
i think it doesn't matter one way or the other.
plumber then upas/fs is the standard way.
neither forks the namespace, so they both
see each other (necessary for plumbing incoming
mail messages).
russ
next reply other threads:[~2002-05-30 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 18:24 rsc [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-10 13:17 presotto
2002-06-07 14:02 Russ Cox
2002-06-10 9:57 ` Gabriel Diaz Lopez de la Llave
2002-06-07 11:34 Fco.J.Ballesteros
2002-06-06 17:23 presotto
2002-06-07 9:06 ` Gabriel Diaz Lopez de la Llave
2002-06-06 14:51 anothy
2002-06-05 12:18 presotto
2002-06-06 13:29 ` Gabriel Diaz Lopez de la Llave
2002-05-30 18:57 rog
2002-05-30 18:40 rog
2002-05-30 18:39 rsc
2002-05-30 18:24 rog
2002-05-30 18:13 rsc
2002-06-05 10:03 ` Gabriel Diaz Lopez de la Llave
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=0b99cba020d43dae0c771e8a591f7c88@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).