From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris McGee <newton688@gmail.com>
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