From: Grant Miner <mine0057@mrs.umn.edu>
To: Mike Fedyk <mfedyk@matchmail.com>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: directory inclusion in ext2/ext3
Date: Wed, 23 Jul 2003 20:24:37 -0500 [thread overview]
Message-ID: <3F1F3555.2020109@mrs.umn.edu> (raw)
In-Reply-To: <20030724005431.GJ1176@matchmail.com>
I would also like this enhancement. Plan 9 is built around this
feature, and it does it as an int argument 'flag' to mount, such that
'flag' may be (these are defined in a header):
MREPL: Replace the old file by the new one. Henceforth, an evaluation of
old will be translated to the new file. If they are directories (for
mount, this condition is true by definition), old becomes a union
directory consisting of one directory (the new file).
MBEFORE: Both the old and new files must be directories. Add the
constituent files of the new directory to the union directory at old so
its contents appear first in the union. After an MBEFORE bind or mount,
the new directory will be searched first when evaluating file names in
the union directory.
MAFTER: Like MBEFORE but the new directory goes at the end of the union.
In addition, there is an MCREATE flag that can be OR'd with any of the
above. When a /create /system call (see /open/(2))
<http://plan9.bell-labs.com/magic/man2html/2/open> attempts to create in
a union directory, and the file does not exist, the elements of the
union are searched in order until one is found with MCREATE set. The
file is created in that directory; if that attempt fails, the /create
/fails.
...
(from http://plan9.bell-labs.com/magic/man2html/2/bind )
Further rationale can be provided if desired; just ask.
next prev parent reply other threads:[~2003-07-24 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 20:22 Re: directory inclusion in ext2/ext3 softpro
2003-07-24 0:54 ` Mike Fedyk
2003-07-24 1:24 ` Grant Miner [this message]
[not found] <cypH.5dM.33@gated-at.bofh.it>
[not found] ` <cCCR.hN.7@gated-at.bofh.it>
2003-07-24 8:37 ` Ihar "Philips" Filipau
-- strict thread matches above, loose matches on Subject: below --
2003-07-24 3:48 Johannes Halmann
2003-07-25 17:10 ` Mike Fedyk
2003-07-23 19:36 softpro
2003-07-23 20:04 ` Scott McDermott
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=3F1F3555.2020109@mrs.umn.edu \
--to=mine0057@mrs.umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
/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).