From: Hans Reiser <reiser@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: George Beshers <gbeshers@comcast.net>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: viewprinting: what format should views be stored in? (let me quickly correct an imprecision)
Date: Tue, 17 Aug 2004 19:37:30 -0700 [thread overview]
Message-ID: <4122C0EA.8010607@namesys.com> (raw)
In-Reply-To: <4122BD60.2090601@namesys.com>
Let me instead of the previous email, say:
For me, the big issue to decide at the start is, should a view
specification be implemented with a format that is as if it is a
subdirectory of the masked executable, and which we then take the
filenames used by the executable and traverse the subdirectory as though
it was root, and if we reach a valid fall through point, then allow we
traverse from the real filesystem root, and if not, we issue a suitable
error.
This would let us use all the semantic tree traversal code already
written by us.
It would however require us to add such plugins as "fall through
points", and "prints", etc. If really lucky, you could have some
working plugins in 4 months, and maybe have masking software done by the
end of the contract.
I think the answer is yes, we want to do it this way, but I am going to
think about it as I jog for an hour. Please come up with arguments for
and against it.
>
> Hans
>
next prev parent reply other threads:[~2004-08-18 2:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 0:15 viewprinting: what format should views be stored in? Hans Reiser
2004-08-16 1:48 ` George Beshers
2004-08-16 2:02 ` Hans Reiser
2004-08-16 13:47 ` George Beshers
2004-08-16 19:50 ` George Beshers
2004-08-17 7:07 ` Hans Reiser
2004-08-17 19:29 ` George Beshers
2004-08-17 20:28 ` Hans Reiser
2004-08-17 23:46 ` George Beshers
2004-08-18 2:22 ` Hans Reiser
2004-08-18 2:37 ` Hans Reiser [this message]
[not found] ` <4121F4D6.8090506@comcast.net>
2004-08-17 19:43 ` Hans Reiser
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=4122C0EA.8010607@namesys.com \
--to=reiser@namesys.com \
--cc=gbeshers@comcast.net \
--cc=reiserfs-list@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 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.