Just to clarify what I meant: I don't see why a FS-like structure
(directory) needs to be presented as a single (atomic) file.
> It is said that editing _huge_ files where only small part changes is
> really slow (if you move things in the file) or really inefficient (if
> you leave gaping holes like MS Word "Quick Save").
>
> This apparently happens when you edit compound documents, like the
> component-based KOffice documents (containing a figure which contains a
> spreadsheet which contains a database etc.)
>
> A fair point, though I haven't seen a convincing argument why a plain
> old directory isn't adequate for holding a compound document.
Exactly my point. Leave it as a directory. Let the GUI pretend that
it's really an atomic entity. Don't hack the kernel or libc to pretend
that some directories are in fact atomic files.
Regards,
Richard....
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/