From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] reverse engineering binds
Date: Thu, 11 Jan 2007 08:58:29 -0800 [thread overview]
Message-ID: <3e1162e60701110858p5a1567e7u2f46fc2bd9c983c@mail.gmail.com> (raw)
In-Reply-To: <1150a56ba13311c844ec052b2735c0a1@quintile.net>
Type "ns" at the shell? That'll tell you how your namespace was built
right? Or am I thinking Inferno again?
On 1/11/07, Steve Simon <steve@quintile.net> wrote:
> I want to discover where a file has come from, I understand that
> it will probably lead back to a /srv descriptor or a network connection
> but that is good enough. I need to walk back up the cd and the list of binds
> in the output of ns(1).
>
> I think this needs care to really get it right, so, has anyone got some
> C or rc that does this or shall I just fumble around until I sort it out
> for myself :-)
>
> Thanks guys,
>
> -Steve
>
next prev parent reply other threads:[~2007-01-11 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 16:45 Steve Simon
2007-01-11 16:58 ` David Leimbach [this message]
2007-01-11 17:32 ` C H Forsyth
2007-01-11 16:52 erik quanstrom
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=3e1162e60701110858p5a1567e7u2f46fc2bd9c983c@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@cse.psu.edu \
/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).