From: Roman Shaposhnick <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] simple questions on bind semantics
Date: Tue, 28 Sep 2004 18:08:58 -0700 [thread overview]
Message-ID: <20040929010858.GD9560@submarine> (raw)
In-Reply-To: <b81160acf78bec3dc8baa000379f4190@vitanuova.com>
On Tue, Sep 28, 2004 at 02:57:42PM +0100, C H Forsyth wrote:
> mntgen(4), for instance, generates names on demand.
mntgen seems new to me (I could bet it wasn't part of the
Plan 9 release 3, but may be I've just overlooked it)
Anyway, is this how one accomplishes what I was trying
to do (bind /existing-file /non-existing-file):
$ mntgen /
$ bind /existing-file /non-existing-file
The one thing that troubles me about this approach is that
all of a sudden any lookup in / starts succeeding.
Thanks,
Roman.
next prev parent reply other threads:[~2004-09-29 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 0:46 Roman Shaposhnick
2004-09-28 0:51 ` Rob Pike
2004-09-28 13:57 ` C H Forsyth
2004-09-29 1:08 ` Roman Shaposhnick [this message]
2004-09-29 1:23 ` andrey mirtchovski
2004-09-29 8:37 ` Fco. J. Ballesteros
2004-09-29 3:13 ` Roman Shaposhnick
2004-09-29 17:06 ` Richard Miller
2004-10-01 17:36 ` Roman Shaposhnick
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=20040929010858.GD9560@submarine \
--to=rvs@sun.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).