Re: reiser4 plugins

From: David Masover
Date: Fri Jul 01 2005 - 04:10:37 EST


Hubert Chan wrote:
On Tue, 28 Jun 2005 15:59:03 -0400, Kyle Moffett <mrmacman_g4@xxxxxxx> said:


On Jun 28, 2005, at 13:51:04, Hubert Chan wrote:


I don't know if VFS is the right place for it, but I agree that it
would be good to make it accessible to all filesystems.


That's somewhat of a contradiction in terms. The whole point of the
VFS is to hold all of the things that multiple filesystems want to
share :-D.


VFS provides a common interface to the filesystem. I don't think metafs
needs any VFS changes. It may be able to get by without making changes
to the VFS, and if so, it shouldn't touch the VFS. It should just be
its own separate filesystem.

I imagine most of it could be implemented by a FUSE filesystem.

"could", yes. "should", no. I'll refer you to my HURD comment.

That's not to say that none of this should be userspace, just that some of it most certainly *never* needs to touch userspace, such as cryptocompress.

I'm not guessing that you wanted to make it FUSE, I just want to be pre-emptive here. FUSE will NOT work well for this.

Maybe we just need better regular applications?


You mean patch them all so that they understand and can edit
xattr/substreams/etc.? The file-as-dir interface is meant to avoid
having to do that. metafs also avoids having to patch all the
applications by exposing them as regular files.

Metafs also avoids having to patch tar. It's assumed that legacy backup systems can always avoid metafs and still catch almost everything important, and certainly everything they already do catch. With a hybrid or an entirely new backup system, we could catch everything, including any new ACL-like animals that people invent.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/