From: "David Dabbs" <david@dabbs.net>
To: 'David Masover' <ninja@slaphack.com>
Cc: reiserfs-list@namesys.com
Subject: RE: Fibration questions
Date: Wed, 21 Jul 2004 00:44:27 -0500 [thread overview]
Message-ID: <20040721054418.1150715C23@mail03.powweb.com> (raw)
In-Reply-To: <40FDFB81.3080701@slaphack.com>
> |>
> |>I must not understand fibration. Do you have to know the fibration of
> |>an object to find it?
> |>
> |
> | Fibration is simply a means to physically group together filesystem
> objects
> =>> MEGA SNIP <<=
>
> So, what you're trying to say is, yes, because it's part of the key?
>
No, not really, at least you (as a filesystem client) don't specify the
fibration when searching for an object. Yes, when the key is generated, of
course the fibration bits matter, but they simply come from a blackbox
plugin function that simply operates on the name and which may differ per
directory. As Hans pointed out, there may be an opportunity to offer some
explicit support for * via the syscall interface -- as to whether or not the
implementation would even involve fibration is open for discussion.
It seems like we are violently agreeing, as my father sometimes says. I too
think it would be great to have an enhanced or more structured typing
system. And it would be interesting to work on at some point, but not just
yet, for me at least. There's still so much to learn about what's here.
Anyway, I've kind of lost track of what it is you were looking to accomplish
in the thread.
Best,
David
next prev parent reply other threads:[~2004-07-21 5:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 10:35 Fibration questions David Dabbs
2004-07-16 11:04 ` Nikita Danilov
2004-07-16 17:45 ` David Dabbs
2004-07-18 7:11 ` Hans Reiser
2004-07-18 7:47 ` David Dabbs
2004-07-19 4:23 ` David Masover
2004-07-19 7:21 ` David Dabbs
2004-07-19 21:34 ` David Masover
2004-07-19 22:06 ` Valdis.Kletnieks
2004-07-19 22:32 ` David Dabbs
2004-07-20 6:03 ` Hans Reiser
2004-07-20 7:03 ` David Masover
2004-07-20 5:30 ` Hans Reiser
2004-07-20 7:07 ` David Masover
2004-07-20 8:31 ` David Dabbs
2004-07-21 5:13 ` David Masover
2004-07-21 5:44 ` David Dabbs [this message]
2004-07-21 6:20 ` David Masover
2004-07-21 6:36 ` David Dabbs
2004-07-21 8:32 ` mjt
2004-07-22 4:08 ` David Masover
2004-07-22 10:06 ` mjt
2004-07-22 18:14 ` Hans Reiser
2004-07-23 2:45 ` David Masover
2004-07-23 9:42 ` mjt
2004-07-23 18:21 ` David Masover
2004-07-22 10:10 ` Vitaly Fertman
2004-07-23 2:43 ` David Masover
2004-07-23 9:09 ` Vitaly Fertman
2004-07-26 6:28 ` Hans Reiser
2004-07-26 10:11 ` Vitaly Fertman
2004-07-23 9:59 ` Christian Mayrhuber
2004-07-23 9:59 ` mjt
2004-07-23 18:13 ` David Masover
2004-07-23 10:05 ` mjt
2004-07-22 8:03 ` Hans Reiser
2004-07-22 12:16 ` Nikita Danilov
2004-07-22 14:39 ` mjt
2004-07-22 18:17 ` Hans Reiser
2004-07-22 18:26 ` mjt
2004-07-22 19:57 ` Valdis.Kletnieks
2004-07-22 21:05 ` mjt
2004-07-22 21:36 ` Valdis.Kletnieks
2004-07-23 9:28 ` mjt
2004-07-23 22:42 ` Valdis.Kletnieks
2004-07-23 2:40 ` David Masover
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=20040721054418.1150715C23@mail03.powweb.com \
--to=david@dabbs.net \
--cc=ninja@slaphack.com \
--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.