> > (a) Because it prevents the normal user from messing around with the
> > internal of the `directory' and with it preventing the application
> > programmer from adding tons of code to detect and workaround unexpected
> > changes.
>
> All proposals so far don't _prevent_ the users, even normal ones, from
> messing around with the internals. Frankly any reliable application is
> going to have to deal with unexpected data in the file anyway.
>
> > (b) The normal user expects a `bunch of data' in a single file, not in a
> > directory.
> > (c) The content of the `directory' isn't of interest to the user but to some
> > applications.
>
> These points merely argue for something that behaves like a directory
> but doesn't look like one in an `ls' listing.
>
> The only compelling reason I can see is:
>
> (1) Ordinary users wish to copy/move compound files as a single unit,
> attach them to emails and put them on web sites.
>
> Which argues for automatic conversion to/from flat form on demand.
> It could be done in user space, and a kernel hook could make it
> transparent for all programs.
If you have http://atrey.karlin.mff.cuni.cz/~pavel/podfuk/podfuk.html
installed, then:
If you have directory, adding #tar at the end makes tar file from
it. If you have tar file, adding #utar at the end makes it look like
directory. ... which is adequate conversion way in my eyes. Doing it
completely automatic would confuse just about everything.
Pavel
PS: The kernel hook is already there. It is called "coda".
-- I'm really pavel@ucw.cz. Look at http://195.113.31.123/~pavel. Pavel Hi! I'm a .signature virus! Copy me into your ~/.signature, please!- 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/