From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <dcdc77e37bf8606b0659ead728ff48ea@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam -r with plan9ports
From: "Russ Cox" <rsc@swtch.com>
Date: Fri, 30 Jun 2006 07:41:25 -0800
In-Reply-To: <82c890d00606300250wc768283h21a113b7f889d06b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 7189e5a4-ead1-11e9-9d60-3106f5b1d025

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