From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris McGee Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Message-Id: <190D5EF8-76CA-40F5-B9ED-FB4233D93749@gmail.com> Date: Wed, 5 Oct 2016 23:06:39 -0400 To: 9fans@9fans.net Subject: [9fans] Cpu command and namespace Topicbox-Message-UUID: a3d07c46-ead9-11e9-9d60-3106f5b1d025 Hi All, I tried running a cpu server using aux/listen1 on one of my plan9 machines a= nd 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 i= mpression that the namespace should come from the client. Am I doing something wrong here or is my understanding incorrect? Maybe I ne= ed to get authentication set up properly? Thanks, Chris= From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <190D5EF8-76CA-40F5-B9ED-FB4233D93749@gmail.com> In-Reply-To: <190D5EF8-76CA-40F5-B9ED-FB4233D93749@gmail.com> From: Skip Tavakkolian Date: Thu, 6 Oct 2016 03:46:51 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a114c98b4817428053e2a25d0 Subject: Re: [9fans] Cpu command and namespace Topicbox-Message-UUID: a3d64608-ead9-11e9-9d60-3106f5b1d025 --001a114c98b4817428053e2a25d0 Content-Type: text/plain; charset=UTF-8 namespace of the client is mounted under /mnt/term. On Wed, Oct 5, 2016 at 8:06 PM Chris McGee 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 > --001a114c98b4817428053e2a25d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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.<= br class=3D"gmail_msg">
When I connected I noticed that the namespace was the local namespace of th= e server, not the namespace of the client before connecting. I was under th= e impression that the namespace should come from the client.

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

Thanks,
Chris
--001a114c98b4817428053e2a25d0-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <7286d4b134dcff6c769ed30d02914bfa@9netics.com> To: 9fans@9fans.net Date: Wed, 5 Oct 2016 21:14:48 -0700 From: Skip Tavakkolian <9nut@9netics.com> In-Reply-To: <190D5EF8-76CA-40F5-B9ED-FB4233D93749@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Cpu command and namespace Topicbox-Message-UUID: a3dd745a-ead9-11e9-9d60-3106f5b1d025 > 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% From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris McGee Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Message-Id: <1BBFD4CE-325A-415A-B0C2-103E7A45437C@gmail.com> Date: Thu, 6 Oct 2016 09:58:45 -0400 References: <7286d4b134dcff6c769ed30d02914bfa@9netics.com> In-Reply-To: <7286d4b134dcff6c769ed30d02914bfa@9netics.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Cpu command and namespace Topicbox-Message-UUID: a3ee4ae6-ead9-11e9-9d60-3106f5b1d025 Thanks Skip, That's the part I was missing. I thought that the current namespace is prese= rved after cpu command on the remote. But then I realize that it would be di= fficult 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 customiz= e 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= . >=20 > perhaps it's a confusion over cwd when you cpu to another machine? >=20 > supermic% pwd > /usr/fst > supermic% cpu -h rpi > rpi% pwd > /usr/fst > rpi%=20 >=20 > 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. >=20 > e.g. >=20 > rpi% devsysname=3D'/dev/sysname' for (i in `{seq 3}) { > echo $devsysname ' =3D ' `{cat $devsysname} > devsysname=3D'/mnt/term'^$devsysname > } > /dev/sysname =3D rpi > /mnt/term/dev/sysname =3D supermic > /mnt/term/mnt/term/dev/sysname =3D dell > rpi%=20 >=20 >=20