From: Keith Nash <kjn9@citizenearth.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Another namespace question
Date: Mon, 3 Mar 2003 17:41:33 +0000 [thread overview]
Message-ID: <20030303174133.15491.qmail@mail.dirac.net> (raw)
This is a question about why namespaces were designed in the way that they were.
The command
bind path1 path2
where both path1 and path2 are directories, makes path2 a union directory consisting of path1 alone. So far, so good.
Why was it decided that this command also does the following:
(a) any union directory previously bound to path2 is automatically unmounted, and is found to have disappeared if the new union directory at path2 is unmounted (this is not the case for Lunix mount); *but*...
(b) ...any union directory previously bound to a subdirectory of path2 is not unmounted.
A possible reason for (a) is to clean up the namespace by removing binds that are invisible; but then why (b)?
Keith.
next reply other threads:[~2003-03-03 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 17:41 Keith Nash [this message]
2003-03-03 18:10 ` Russ Cox
2003-03-03 18:14 ` David Presotto
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=20030303174133.15491.qmail@mail.dirac.net \
--to=kjn9@citizenearth.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).