From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Cpu command and namespace
Date: Wed, 5 Oct 2016 21:14:48 -0700 [thread overview]
Message-ID: <7286d4b134dcff6c769ed30d02914bfa@9netics.com> (raw)
In-Reply-To: <190D5EF8-76CA-40F5-B9ED-FB4233D93749@gmail.com>
> 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%
next prev parent reply other threads:[~2016-10-06 4:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 3:06 Chris McGee
2016-10-06 3:46 ` Skip Tavakkolian
2016-10-06 4:14 ` Skip Tavakkolian [this message]
2016-10-06 13:58 ` Chris McGee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7286d4b134dcff6c769ed30d02914bfa@9netics.com \
--to=9nut@9netics.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).