From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fd2path and devsrv
Date: Wed, 19 Nov 2008 23:14:52 -0500 [thread overview]
Message-ID: <bc8e37041f11188f9c29ac47fc8f5cc2@quanstro.net> (raw)
In-Reply-To: <A360C396-4AD5-4728-8E1A-3F8C6BE87A75@sun.com>
> 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 in pointing out the nits, i missed the point.
according to the ns(1) man page
[...]The out-
put is in the form of an rc(1) script that could, in princi-
ple, recreate the name space. The output is produced by
reading and reformatting the contents of /proc/pid/ns.
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.
perhaps you want a new program, nsroot that does
what you suggest.
- erik
next prev parent reply other threads:[~2008-11-20 4:14 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 [this message]
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=bc8e37041f11188f9c29ac47fc8f5cc2@quanstro.net \
--to=quanstro@quanstro.net \
--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).