From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Russ Cox <rsc@swtch.com>, serge.gagnon@b2b2c.ca
Subject: Re: [9fans] p9p plumber
Date: Sat, 4 Mar 2006 15:04:28 -0600 [thread overview]
Message-ID: <20060304210428.2A9C610C6A@dexter-peak.quanstro.net> (raw)
In-Reply-To: <090bcf9eac9bf3a7231de21732c84587@swtch.com>
make sure the permissions on the directory are 700.
it won't work without that.
- erik
"Russ Cox" <rsc@swtch.com> writes
|
| You need to create a name space directory and
| set $NAMESPACE. Since the machines I use are all
| single-user, I typically just use the machine name:
|
| h=`{hostname}
| NAMESPACE=/tmp/ns.$h
| mkdir -p $NAMESPACE
|
| See intro(4) for information about name space directories.
|
| Russ
next prev parent reply other threads:[~2006-03-04 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 19:54 Serge Gagnon
2006-03-04 20:06 ` Russ Cox
2006-03-04 21:04 ` erik quanstrom [this message]
2006-03-04 21:20 ` Russ Cox
2006-03-04 21:26 ` erik quanstrom
2006-03-04 22:34 ` erik quanstrom
2006-03-04 21:38 ` Serge Gagnon
2006-03-04 22:21 ` erik quanstrom
2006-03-04 22:42 ` Serge Gagnon
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=20060304210428.2A9C610C6A@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
--cc=serge.gagnon@b2b2c.ca \
/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).