From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Is this weird?
Date: Wed, 14 Jun 2000 20:32:05 +0100 [thread overview]
Message-ID: <200006141930.PAA24631@cse.psu.edu> (raw)
>>Maybe you guys misunderstood the question. Basicall I'm getting a
sorry. we ought to have answered your question before starting
a subdiscussion. when you list a union mount, you'll see the contents
of each directory in turn. in particular, if you unite a directory with itself,
however many times, you'll see the files in each instance (ie, names repeated).
try something like
mkdir m
>m/x
bind -b m m
ls m
bind -b m m
ls m
...
in your case, as rob suggested, you've most likely done something that
caused /net to be bound to itself. i'd guess that, not #I alone
being bound twice, because ether0 (#l) is there as well.
often when the same names appear, they really do come from different
directories in the union. ls -q prints Qid data that helps to distinguish
them, hence rob's suggestion of ls -lq. in your case, duplicate names
should have the same qids (because they are the same file).
another helpful option is -n, which tells ls not to sort the result, so names
appear in the order they are seen in the union, allowing you to tell which
duplicate is uppermost (and thus selected by the system in a search).
next reply other threads:[~2000-06-14 19:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-14 19:32 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-14 23:48 presotto
2000-06-14 18:52 rob pike
2000-06-14 18:39 Russ Cox
2000-06-14 17:41 forsyth
2000-06-14 17:55 ` James G. Stallings II
2000-06-14 18:31 ` Andrey Mirtchovski
2000-06-14 17:56 ` Alexander Viro
2000-06-15 5:57 ` C H Forsyth
2000-06-14 16:58 James G. Stallings II
2000-06-14 17:26 ` Alexander Viro
2000-06-14 17:36 ` James G. Stallings II
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=200006141930.PAA24631@cse.psu.edu \
--to=forsyth@vitanuova.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).