From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] any reason not to have srv in namespace?
Date: Fri, 28 Mar 2003 14:14:27 -0500 [thread overview]
Message-ID: <4da726d2f0b1704627da8d83693168b3@plan9.bell-labs.com> (raw)
In-Reply-To: <db2ee7a8105e55024837b675b3f9410e@plan9.escet.urjc.es>
I don't think srv should be there.
For one thing, it's too big and clunky.
Cpurc and termrc exist to set up
the initial environment. Namespace
is for setting up a new name space
from the existing environment.
prev parent reply other threads:[~2003-03-28 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 19:07 Fco.J.Ballesteros
2003-03-28 19:14 ` Russ Cox [this message]
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=4da726d2f0b1704627da8d83693168b3@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).