From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] simple questions on bind semantics
Date: Wed, 29 Sep 2004 10:37:57 +0200 [thread overview]
Message-ID: <6b12d0bfb358061d580739764da4d018@plan9.escet.urjc.es> (raw)
In-Reply-To: <92dc2b3a1981e3c73d938d7ae6a0d3a9@plan9.ucalgary.ca>
>> Anyway, is this how one accomplishes what I was trying
>> to do (bind /existing-file /non-existing-file):
In Plan B we used to have a prefix table (now it's gone).
There you could say something like
/a/path/I/just/invented -goes-to-> a-file-server
This has the net effect that you can invent paths.
It was not that useful. I mean, you can perfectly do without
inventing files. Sometimes I missed this to patch up CDs, but
that's a different issue.
hth
next prev parent reply other threads:[~2004-09-29 8:37 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
2004-09-29 1:23 ` andrey mirtchovski
2004-09-29 8:37 ` Fco. J. Ballesteros [this message]
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=6b12d0bfb358061d580739764da4d018@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--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).