From: a@9srv.net
To: 9fans@9fans.net
Subject: [9fans] Unintuitive mount behavior
Date: Tue, 9 Apr 2013 16:56:12 -0400 [thread overview]
Message-ID: <80f440ac009d67c54e1ac6ed82d2b093@9srv.net> (raw)
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
:; bind dog/mutt pig/tabby
:; cat cat/tabby
woof
That is not what I'd expect, and certainly not what the 9fan
originally asking the question expected. I presume this is
because the device and qid match, but can't track down
exactly where. Is this because the path from Qids, instead
of Chans, is being used in /sys/src/9/port/chan.c?
Anthony
next reply other threads:[~2013-04-09 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 20:56 a [this message]
2013-04-09 21:05 ` Nemo
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=80f440ac009d67c54e1ac6ed82d2b093@9srv.net \
--to=a@9srv.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).