From: Al Viro <viro@zeniv.linux.org.uk>
To: Blake McBride <blake@mcbridemail.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"brauner@kernel.org" <brauner@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Colby Wes McBride <colbym84@gmail.com>
Subject: Re: [RFC] View-Based File System Model with Program-Scoped Isolation
Date: Thu, 4 Sep 2025 23:06:50 +0100 [thread overview]
Message-ID: <20250904220650.GQ39973@ZenIV> (raw)
In-Reply-To: <Oa1N9bTNjTvfRX39yqCcQGpl9FJVwfDT2fTq-9NXTT8HqTIqG2Y-Gy0f7QHKcp2-TIv7NZ3bu_YexmKiGuo9FBTeCtRnVzABBVnhx5EiShk=@mcbridemail.com>
On Thu, Sep 04, 2025 at 09:52:22PM +0000, Blake McBride wrote:
> Proposed Model
> --------------
> The key concept is the introduction of *views*. A view is a named,
> use-case-specific file hierarchy that contains a subset of the overall
> files on the system. Each view presents its own hierarchy, which can
> be completely different from others. Files may appear in multiple
> views, and may even have different names per view.
What happens on cross-directory rename? Within the same "view", that is.
How does it map to changes observable in other views of yours?
next parent reply other threads:[~2025-09-04 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Oa1N9bTNjTvfRX39yqCcQGpl9FJVwfDT2fTq-9NXTT8HqTIqG2Y-Gy0f7QHKcp2-TIv7NZ3bu_YexmKiGuo9FBTeCtRnVzABBVnhx5EiShk=@mcbridemail.com>
2025-09-04 22:06 ` Al Viro [this message]
2025-09-04 22:58 ` [RFC] View-Based File System Model with Program-Scoped Isolation Blake McBride
2025-09-04 23:08 ` Al Viro
2025-09-04 23:41 ` Blake McBride
2025-09-04 23:57 ` Blake McBride
2025-09-05 0:06 ` Blake McBride
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=20250904220650.GQ39973@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=blake@mcbridemail.com \
--cc=brauner@kernel.org \
--cc=colbym84@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.