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 21:05:15 -0800 [thread overview]
Message-ID: <9768FEC3-5CF6-4CD6-A1BE-6E33A9705BA6@sun.com> (raw)
In-Reply-To: <bc8e37041f11188f9c29ac47fc8f5cc2@quanstro.net>
On Nov 19, 2008, at 8:14 PM, erik quanstrom wrote:
>> On Nov 19, 2008, at 7:32 PM, erik quanstrom wrote:
>>>> 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
>>>> %
>>>
>>> ; mount /net/il/0/data /n/x
>>> mount: mount /n/x: version conversion
>>
>> Huh? What gives -- of course I ran my example
>> in 9vx, but it shouldn't matter -- should it?
>
> your example does work; mine was a counter example.
But now I'm curious -- why didn't it work?
> so following fd2path along its merry way down
> to the source doesn't help generating such a script.
> i could think of cases where it would be a hinderance.
Fair enough. It does, invalidate the example given by
Rob in his article though:
-------------------------------------------------------------------------------
Another program, ns, does this; it reads the /proc/n/ns file, decodes
the information,
and interprets it, translating the network addresses and quoting the
names when required:
...
mount -a ’#s/dns’ /net
...
mount -c il!135.104.3.100!12884 /mnt/term
-------------------------------------------------------------------------------
Thanks,
Roman.
next prev parent reply other threads:[~2008-11-20 5:05 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
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 [this message]
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=9768FEC3-5CF6-4CD6-A1BE-6E33A9705BA6@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).