From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <82c890d00607070129r7e1ef0fakee18942ee6e2908c@mail.gmail.com>
Date: Fri,  7 Jul 2006 10:29:15 +0200
From: "Gabriel Diaz" <gabidiaz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] sam -r with plan9ports
In-Reply-To: <dcdc77e37bf8606b0659ead728ff48ea@swtch.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <82c890d00606300250wc768283h21a113b7f889d06b@mail.gmail.com>
	<dcdc77e37bf8606b0659ead728ff48ea@swtch.com>
Topicbox-Message-UUID: 749695da-ead1-11e9-9d60-3106f5b1d025

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
>
>