Jeremy Maitin-Shepard wrote: > David Masover <[EMAIL PROTECTED]> writes: > > [snip] > > >>>I have. And have seen /no/ benefit to you. Except, of course, the benefit >>>accrued from some magic in Linus' kernel, by which all format differences >>>go in a puff of smoke if they are implemented inside it, and furthermore >>>all userland gets rebuilt to use the kernel's way overnight. > > >>Let's say cryptocompress gets implemented. Not all of userland >>rewritten, not even any of userland rewritten, just a cryptocompress >>plugin for the kernel. And instead of having to learn a new tool, I can >>just browse around in /meta. > > > What is the relationship between file-as-dir or special meta-data and > transparent encryption+compression? I do not see why file-as-dir would > require such a special interface.
I'm ignoring file-as-dir until/unless someone figures out a sane way of doing it. Under Reiser4, think of all files/directories as objects. Meta-data, as accessed through file-as-dir or through /meta, is just a collection of methods to that file/directory. Some methods are just accessor (setter/getter) methods, like foo.mp3/artist -- they are effectively attributes, although there may be a little more logic going on there (foo.mp3/artist probably is connected to foo.mp3's id3 tag). Some methods actually do something, like secret.txt/compression. The reason I'm bringing that up is that some people seem determined to keep the very concept out of the kernel because it's new, strange, and doesn't seem to have any real applications. I want it in because it has real, fairly immediate applications, and much bigger payoffs down the road, and I don't think it's that strange -- it's a nice, clean design. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
