From: David Masover <ninja@slaphack.com>
To: David Dabbs <david@dabbs.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Fibration questions
Date: Wed, 21 Jul 2004 00:13:37 -0500 [thread overview]
Message-ID: <40FDFB81.3080701@slaphack.com> (raw)
In-Reply-To: <20040720083108.73C4C15DCA@mail03.powweb.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Dabbs wrote:
|>Hans Reiser wrote:
|>| David Masover wrote:
|>|
|>|> Why beyond? Ask each fs object (without knowing its name), "What is
|>|> your primary type?" Put like-typed objects together. Simple.
|>|
|>| Except that at look up time all you know is the name, and if the type is
|>| not in the name then you cannot fibrate by it.
|>
|>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?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQP37gHgHNmZLgCUhAQJ0xxAAjsgWwIjjrM/mjZTkWgR0L5ih3bAIdWhB
gXZtcXkzqOYkEi4slSdBpGaTgz1UytuS6eKWSU46sRTQAp9AOH9RAJrdPYBWCKHQ
K1TGRqK+BhbM8Ygk7B389zr84KO8wI+ekY5a2ErAYNZ+s41xztBfC0SsMPdzTflQ
T2ePnPzRQjImARjwhYELgXsUVDmXM9nO694oLoYhUvdRzMZfpEeL/S1duCbtr4zQ
o7FCk487opiE4q0HfRS+dXdJh06daOKI0uCKUZWCVeZkKoASaCo9Zy8rVfdLORUp
weRSfONRS2l/DHgpu0hfmnZ3GSfTijugDzvGt6L8Xgae++sj7FcoRWVUK3QNWlwg
M74dRy85vPEYdflHAqqD8az1AGVsj6DWz/GcXpwQH7gutfpcmk6rdKgxt0YlLC3p
NEAtqHwT/S7T1/7ya8L9UU5kqub861xiJ1NZacZ1V0YTN8jLAxeXqX3lGNJMYnPy
Vo+esgMGFbksFV4adS27tbX1jxLbn/Y9s1A9UdMmqN7td6APEXzIafwcWo+jBZdS
TXWEletyoT5CbtrUISlXzgb9CWFhyzofwtl6wHR3NBuSmesIsgtBZi7/nil1TDX9
y7w3Hrhpgd1at2ch0JsnB+X5J7jdjgvQMmKBms0y/qk6r/KLP5hRMjrA73YmBrup
rEhzNyWMzgo=
=8NIG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-21 5:13 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 [this message]
2004-07-21 5:44 ` David Dabbs
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=40FDFB81.3080701@slaphack.com \
--to=ninja@slaphack.com \
--cc=david@dabbs.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.