From: Nemo <nemo.mbox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Unintuitive mount behavior
Date: Tue, 9 Apr 2013 23:05:06 +0200 [thread overview]
Message-ID: <B4A7794E-03A6-4611-A675-8D05E7C11D52@gmail.com> (raw)
In-Reply-To: <80f440ac009d67c54e1ac6ed82d2b093@9srv.net>
On Apr 9, 2013, at 10:56 PM, a@9srv.net wrote:
> This came up in #plan9, and I reduced it to this example:
>
> :; mkdir cat dog pig
> :; echo meow > cat/tabby
> :; echo woof > dog/mutt
> :; bind cat pig
When you reach pig, you now jump to cat.
> :; bind dog/mutt pig/tabby
You resolve pig/tabby before the bind, which means
cat/tabbly because of the bind
> :; cat cat/tabby
> woof
And there your are.
That's unless I'm too sleepy, of course.
I had problems with mount tables because I came from unix.
Here they are just "jump here to there", but it's hard to assume,
at least to me, because it's too simple for what I'd expect, perhaps.
prev parent reply other threads:[~2013-04-09 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 20:56 a
2013-04-09 21:05 ` Nemo [this message]
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=B4A7794E-03A6-4611-A675-8D05E7C11D52@gmail.com \
--to=nemo.mbox@gmail.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).