I'm curious why the fibration function prototypes take an inode* (that is
unused)? I looked at struct_inode and I can't see anything that looks
helpful to calculating a fibre.
/* fibration.c: sample fibration_plugin.fibre() function proto */
static __u64 fibre_dot_o(const struct inode *dir, con
David Dabbs writes:
>
>
> I'm curious why the fibration function prototypes take an inode* (that is
> unused)? I looked at struct_inode and I can't see anything that looks
> helpful to calculating a fibre.
This for more advanced fibration plugins that keep some per-directory
state (none at
David Dabbs wrote:
While I'm a reiser4 'true believer,' other VFS filesystems do and will
continue to exist. Might an application developer's job be complicated if
not every filesystem for which it presents a file list supports metas or
some means to query file objects' type?
|
Maybe I sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Dabbs wrote:
|>David Dabbs wrote:
[...]
| [David Dabbs]
| The files don't really know their type. The filesystem/OS is deducing
this,
| yes?
Yes and no. Yes, at first, to support apps which don't set a type on
files they create. No, because aft
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 t
>
> 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 the
-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 y
> |>
> |>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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Dabbs wrote:
|>|>
|>|>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 yo
> |
> | 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 whic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nikita Danilov wrote:
| Ask Peter Braam ([EMAIL PROTECTED]), whether he has any plans to use
| reiser4 as a back-end.
I've never used Lustre, but I've heard it implements at least some ideas
from InterMezzo, which used other filesystems (supposedly ANY
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vitaly Fertman wrote:
|>First question: Can I manually enable/disable a particular plugin for a
|>particular directory? (like how cryptocompress is supposed to be...)
|
|
| you can change a plugin for a file if it does not destroy its structure.
| Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Törnqvist wrote:
| Anyway, setting propagation is important, but it's also important to
| handle conditions like (cool, pseudo-sql! ;)
| UPDATE formatting SET policy='never\0' WHERE policy='smart\0' RECURSE;
| instead of just
| UPDATE formatting
> wait -- what does this do:
> echo -e "tea\0" > somedir/metas/plugin/hash
will set the hash tea in 'somedir' if it is empty.
if it has 'subdir' already, nothing happens.
> echo -e "something_differenet\0" > somedir/subdir/metas/plugins/hash
will set the hash 'something_differenet' if any of [r5
On Thu, Jul 22, 2004 at 05:36:43PM -0400, [EMAIL PROTECTED] wrote:
>
>This of course explains why IE is the premier web browser on 95% of the
>desktops, right? I mean, it's faster and more secure than all the alternatives,
>right? ;)
I think desktops for all the Joe Q. Averages are pretty much a d
On Thu, Jul 22, 2004 at 09:45:26PM -0500, David Masover wrote:
>| UPDATE formatting SET policy='never\0' WHERE policy='smart\0' RECURSE;
>| instead of just
>| UPDATE formatting SET policy='never\0' RECURSE;
>| which may break something else...
>
>Both should be allowed. Can that be done now? And
On Thursday 22 July 2004 12:10, Vitaly Fertman wrote:
> > First question: Can I manually enable/disable a particular plugin for a
> > particular directory? (like how cryptocompress is supposed to be...)
>
> you can change a plugin for a file if it does not destroy its structure.
> Thus for an emp
On Fri, Jul 23, 2004 at 11:59:23AM +0200, Christian Mayrhuber wrote:
>It would be a good idea if the meta filesystem interface always auto
>terminates strings (add + '\0') issued by echo. procfs does it that way.
Or add a small parser that allows \n so that cat output would look
better...
--
mj
On Fri, Jul 23, 2004 at 11:59:23AM +0200, Christian Mayrhuber wrote:
>
>So if one does
># echo -e "tea" > somedir/metas/plugin/hash
>it can crash reiser4, because of a non terminated C string?
I also meant to say that Reiser4 just silently ignores the request,
at least last time I checked...
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Törnqvist wrote:
| On Fri, Jul 23, 2004 at 11:59:23AM +0200, Christian Mayrhuber wrote:
|
|>It would be a good idea if the meta filesystem interface always auto
|>terminates strings (add + '\0') issued by echo. procfs does it that way.
|
|
| Or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Markus Törnqvist wrote:
| On Thu, Jul 22, 2004 at 09:45:26PM -0500, David Masover wrote:
|
|>| UPDATE formatting SET policy='never\0' WHERE policy='smart\0' RECURSE;
|>| instead of just
|>| UPDATE formatting SET policy='never\0' RECURSE;
|>| which may
On Fri, 23 Jul 2004 12:28:49 +0300, Markus =?UNKNOWN?Q?T=F6rnqvist?= said:
> I think desktops for all the Joe Q. Averages are pretty much a different
> scene from servers..
It's not as different as you might think. Remember in most corporations that use
Active Directory, all the infrastructure b
22 matches
Mail list logo
