[9fans] sam -r with plan9ports

[9fans] sam -r with plan9ports

[Gabriel Diaz]

Hello,

Is there any trick to use B on a remote machine to open files in a
local samterm?

localhost# sam -r somehost
-----
localhost# ssh somehost
somehost# B file

and file opens up in local host.

I can use B fine while editing locally.


thanks

gabi

Re: [9fans] sam -r with plan9ports

[Russ Cox]

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

Re: [9fans] sam -r with plan9ports

[Gabriel Diaz]

Hello

Thank you very much, somehow this mail got archived in gmail and i
did't saw it until now :(

Gabi

On 6/30/06, Russ Cox <rsc@swtch.com> wrote:
> 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
>
>

Re: [9fans] sam -r with plan9ports

[Gabriel Diaz]

Hello

if i start sam inside the environment you comment, i obtain a blank
window with no error messages.

and if i close it and run B i got

samterm: initdraw: muxrpc: unexpected eof

Is this related to the new way dedraw works?

thanks


gabi


On 6/30/06, Russ Cox <rsc@swtch.com> wrote:
> 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
>
>