From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fd2path and devsrv
Date: Wed, 19 Nov 2008 19:31:42 -0800 [thread overview]
Message-ID: <59F7E2FC-7FFD-4A31-9821-21AA679F9921@sun.com> (raw)
In-Reply-To: <998fbeea126caa967d58924a3b8433f6@quanstro.net>
On Nov 19, 2008, at 6:55 PM, erik quanstrom wrote:
>>> i think the answer to your question is that it's a lot more useful
>>> to know that it's #s/boot rather than /net/il/0/data.
>> Really? Why? With /net/il/0/data you have an option of digging
>> deeper and
>> finding out the other end's address, etc. Or to flip the question
>> -- what
>> information does #s/boot provide?
>
> the reason why #s/boot is useful is twofold. the name means
> something.
#s/boot is a bit special but I get your general point. So, let me
rephrase:
the usefulness of #s/foo is determined by the naming convention.
> this is a connection to the fs used to boot the machine. second, /
> net/il/0/data
> can't be mounted.
Sure it can:
% srv tcp!sources.cs.bell-labs.com!9fs test
% ls /net/tcp
/net/tcp/0
/net/tcp/1
/net/tcp/2
/net/tcp/clone
% mount -n /net/tcp/2/data /n/test
%
> if you want the name of something to mount, ns gives
> you want you want.
Not really, what gets mounted is a Chan to /net/tcp/*/data
as far as I cat tell.
> why are you complaining that ns gives you the most useful
> information?
I'm not complaining about /proc/*/ns I'm complaining about ns(1)
which already does some translations of raw data from /proc/*/ns
but not this particular one.
Thanks,
Roman.
next prev parent reply other threads:[~2008-11-20 3:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 17:45 Roman V. Shaposhnik
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 [this message]
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=59F7E2FC-7FFD-4A31-9821-21AA679F9921@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).