From: Hans Reiser <reiser@namesys.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org,
Alexander Zarochentcev <zam@namesys.com>,
vs <vs@thebsh.namesys.com>
Subject: Re: [PATCH - EXPERIMENTAL] files with forks in the VFS
Date: Sun, 05 Sep 2004 22:59:17 -0700 [thread overview]
Message-ID: <413BFCB5.4010608@namesys.com> (raw)
In-Reply-To: <16699.44411.361938.856856@cse.unsw.edu.au>
Neil Brown wrote:
>As a followup to the multi-branching threads about reiser4, I would
>like to present this patch for discussion and exploration.
>It implements files with fork (which are quite different to files that
>provide different views via a subdirectory structure).
>
>
How are they different? Having a distinguished file is consistent with
the reiser4 approach.
>See Documentation/filesystems/forks.txt (after applying the patch) for more detail.
>
>This is not "how it should be done" but rather "how it could be done",
>and is intended primarily to provide a base for experimentation and
>exploration.
>
>Below is a sample of what can be done, and then the patch.
>
>NeilBrown
>
>
next prev parent reply other threads:[~2004-09-06 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 0:21 [PATCH - EXPERIMENTAL] files with forks in the VFS Neil Brown
2004-09-06 5:59 ` Hans Reiser [this message]
2004-09-06 23:04 ` Neil Brown
2004-09-07 19:31 ` Hans Reiser
2004-09-08 0:27 ` Neil Brown
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=413BFCB5.4010608@namesys.com \
--to=reiser@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=vs@thebsh.namesys.com \
--cc=zam@namesys.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