Re: "Why Reuser 4 still is not in" doc

Jan Engelhardt
2006-07-17T09:43:09Z

>> > (aside from the VFS integration debate)
>> Anybody know what's in Reiser4 that VFS doesn't like (link please)?
>
> Reiser4 plug-ins have (had?) the ability to alter the semantics of things, like
> making files into directories inside

Yes, it changes the semantics. Suddenly you can "cd linux-2.6.17.tar.bz2".
But what will stat() return? S_IFDIR? S_IFREG? S_IFANY? A .tar parser in
kernelspace is almost never the right thing. And then a cpio parser,
because that's what initramfs'es are made of. Not to forget .zip, because
that's omnipresent. Oh of course we'd also need bzip2 and gzip decoder.
BASE64 and UU anyone?

> which you could see meta-files like
> file/uid and file/size which contained meta-data and such accessible as normal
> files to all the unix tools (which is a very good idea IMO). You could get
> things like chmod by just 'echo root
>> file/owner' or something, very nice.

I wish you a lot of fun with users in LDAP or other exotic storage methods.
By making Everything possible through echo, you are violating the unix
philosophy that one tool should do one thing (though echo does just that).
And in this case, echo would be chown, chmod, tar, bzip2 all at once. This
sounds familiar, I think I have seen this with explorer.exe (and its
uncountable DLLs), which lets you change everything within the same
window.

What I think is promising are the compression/encryption plugins. ext2
and 3 had an attribute (`lsattr`) for compression but it does not seem like
ever implemented.

> This was frowned upon by kernel developers who felt that it belonged in the
> kernel VFS (if at all), rather than in reiser4 directly.

Jan Engelhardt
--