[9fans] Cpu command and namespace

[9fans] Cpu command and namespace

[Chris McGee]

Hi All,

I tried running a cpu server using aux/listen1 on one of my plan9 machines and running cpu from another to connect to it. I set auth to none for now.

When I connected I noticed that the namespace was the local namespace of the server, not the namespace of the client before connecting. I was under the impression that the namespace should come from the client.

Am I doing something wrong here or is my understanding incorrect? Maybe I need to get authentication set up properly?

Thanks,
Chris

Re: [9fans] Cpu command and namespace

[Skip Tavakkolian]

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

namespace of the client is mounted under /mnt/term.


On Wed, Oct 5, 2016 at 8:06 PM Chris McGee <newton688@gmail.com> wrote:

> Hi All,
>
> I tried running a cpu server using aux/listen1 on one of my plan9 machines
> and running cpu from another to connect to it. I set auth to none for now.
>
> When I connected I noticed that the namespace was the local namespace of
> the server, not the namespace of the client before connecting. I was under
> the impression that the namespace should come from the client.
>
> Am I doing something wrong here or is my understanding incorrect? Maybe I
> need to get authentication set up properly?
>
> Thanks,
> Chris
>

[-- Attachment #2: Type: text/html, Size: 1128 bytes --]

Re: [9fans] Cpu command and namespace

[Skip Tavakkolian]

>  I was under the impression that the namespace should come from the client.

perhaps it's a confusion over cwd when you cpu to another machine?

supermic% pwd
/usr/fst
supermic% cpu -h rpi
rpi% pwd
/usr/fst
rpi%

since typically everything is served by fs, it is all the same
content.  the local namespace is exported by the local cpu and the
far-end cpu mounts it on /mnt/term.

e.g.

rpi% devsysname='/dev/sysname' for (i in `{seq 3}) {
	echo $devsysname ' = ' `{cat $devsysname}
	devsysname='/mnt/term'^$devsysname
	}
/dev/sysname  =  rpi
/mnt/term/dev/sysname  =  supermic
/mnt/term/mnt/term/dev/sysname  =  dell
rpi%

Re: [9fans] Cpu command and namespace

[Chris McGee]

Thanks Skip,

That's the part I was missing. I thought that the current namespace is preserved after cpu command on the remote. But then I realize that it would be difficult to remap the bin namespaces to a different cpu architecture.

I suppose that I can always bind over what I want from /mnt/term or customize the profile script to do it automatically in cpu case.

Chris

On Oct 6, 2016, at 12:14 AM, Skip Tavakkolian <9nut@9netics.com> wrote:

>> I was under the impression that the namespace should come from the client.
> 
> perhaps it's a confusion over cwd when you cpu to another machine?
> 
> supermic% pwd
> /usr/fst
> supermic% cpu -h rpi
> rpi% pwd
> /usr/fst
> rpi% 
> 
> since typically everything is served by fs, it is all the same
> content.  the local namespace is exported by the local cpu and the
> far-end cpu mounts it on /mnt/term.
> 
> e.g.
> 
> rpi% devsysname='/dev/sysname' for (i in `{seq 3}) {
>    echo $devsysname ' = ' `{cat $devsysname}
>    devsysname='/mnt/term'^$devsysname
>    }
> /dev/sysname  =  rpi
> /mnt/term/dev/sysname  =  supermic
> /mnt/term/mnt/term/dev/sysname  =  dell
> rpi% 
> 
>