Christer Weinigel wrote: > all applicatons that copy files will fail to copy the streams. So > no working cp command, no nautilus nor konqueror without changes to > the application.
No true. A lot of the fancy stuff depends on metadata which is merely another view of the serialised contents in the flat file. Nautilus & Konqueror thumbnails are an example of that (I gave a few more in other mails). cp works fine with that, and so does ftp. The metadata is just recalculated when it's needed from the target file. > And if you have to change the applications anyway, isn't it much > better to agree on a shared library in userspace that everyone uses? > Which has the added bonus that it can be made to work on top of > Linux, Windows, Ultrix and VMS? Ideally yes, a shared library _or_ at least an agreed representation. However, with filesystem support you can improve performance by avoiding unneed serialisation (write to your huge *Office presentation, read it from another program, no need to wait for the slow tar+compress stage yet it's _as if_ those were done), retain computed metadata with coherency guarantees (e.g. real time search indexes, crypto digests and such), and let the filesystem decide when best to prune computed metadata or convert representations. All of these things can work with a combination of userspace plugins (not the same as reiser4 plugins), and filesystem support. Without the filesystem support, you can still use the userspace plugins -- so apps would still be portable -- but you don't get the extras mentioned above. -- Jamie