From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam -r with plan9ports
Date: Fri, 30 Jun 2006 07:41:25 -0800 [thread overview]
Message-ID: <dcdc77e37bf8606b0659ead728ff48ea@swtch.com> (raw)
In-Reply-To: <82c890d00606300250wc768283h21a113b7f889d06b@mail.gmail.com>
It takes a few steps, because you need the local samterm
talking to the same plumber that your remote B is.
See import(4) (9 man 4 import):
EXAMPLE
Suppose you run sam -r to the CPU server anna. Sam wants to
talk to a plumber on the local terminal, but the file names
will refer to files on anna.
To fix this problem, create a new name space directory and
start a new plumber on anna:
remotens=/tmp/ns.`whoami`.on.`hostname`
ssh anna mkdir $remotens
ssh anna NAMESPACE=$remotens plumber
Now import that plumber to the local name space before
starting sam and 9term:
NAMESPACE=/tmp/ns.anna
mkdir $NAMESPACE
import -n $remotens -s plumb anna
sam &
9term ssh anna &
In the shell running in that final ssh you will need to set $NAMESPACE too.
(To /tmp/ns.you.on.localmachine)
Russ
next prev parent reply other threads:[~2006-06-30 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 9:50 Gabriel Diaz
2006-06-30 15:41 ` Russ Cox [this message]
2006-07-06 19:47 ` Gabriel Diaz
2006-07-07 8:29 ` Gabriel Diaz
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=dcdc77e37bf8606b0659ead728ff48ea@swtch.com \
--to=rsc@swtch.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).