9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Roman V. Shaposhnik" <rvs@sun.com>
To: 9fans <9fans@9fans.net>
Subject: [9fans] fd2path and devsrv
Date: Wed, 19 Nov 2008 09:45:45 -0800	[thread overview]
Message-ID: <1227116745.19266.342.camel@goose.sun.com> (raw)

Hi Guys,

I was rereading selected places of Rob's "Getting Dot-Dot Right"
paper and it suddenly occurred to me that the example he provides
there is something that I have always wanted to have. Here it is:
   % cat /proc/125099/ns
   .....
   mount -c /net/il/134/data /mnt/term
   ....
   cd /usr/rob

And, of course, if you run ns(1) it gets even better:
   % ns
   ...
   mount -c il!135.104.3.100!12884 /mnt/term
   ...

Now, when I happen to be logged into the Plan9 the best I can
see is this:
   % cat /proc/2012/ns
   ....
   mount '#s/sources' /n/sources
   ....
Which is fair (the mount really did have /srv/sources as an argument)
but makes me ask the next question: how can Rob's experience be
achieved here? How can I get to the Channel (with the hope of invoking
fd2path) that was given to devsrv when /srv/sources was created?

Thanks,
Roman.




             reply	other threads:[~2008-11-19 17:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 17:45 Roman V. Shaposhnik [this message]
2008-11-19 19:36 ` Francisco J Ballesteros
2008-11-20  1:37   ` Roman V. Shaposhnik
2008-11-20  1:41     ` erik quanstrom
2008-11-20  2:56       ` Roman V. Shaposhnik
2008-11-20  2:55         ` erik quanstrom
2008-11-20  3:31           ` Roman Shaposhnik
2008-11-20  3:32             ` erik quanstrom
2008-11-20  3:57               ` Roman Shaposhnik
2008-11-20  4:14                 ` erik quanstrom
2008-11-20  5:05                   ` Roman Shaposhnik
2008-11-20  9:44   ` roger peppe
2008-11-20 12:59     ` Steve Simon
2008-11-20 13:50       ` roger peppe

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=1227116745.19266.342.camel@goose.sun.com \
    --to=rvs@sun.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).