I think I was badly misunderstood, it's all optional.... (was Re: Summary of how linux can best avoi

Hans Reiser (reiser@ceic.com)
Thu, 1 Jul 1999 16:09:36 +0000 (/etc/localtime)

If you don't create a file with the same name as the directory, and set
it to inherit the body of the files in the directory, and modify all of
the files to inherit the stat data of the directory (I'll not specify
how inheritance gets turned on, I need to think about several
alternatives some more, I like the loic@ceic.com /fscontrol idea
though...), and you don't read/write to files that begin with ".." in the
filename without first creating them (creating a file with the same name
as the filter overrides the filter), then you remain blissfully unaware
of these changes. You are welcome to suggest a better prefix than ".."
for me to give special meaning to it.

Did you really think I would make it somehow mandatory? No wonder you
guys were in a tizzy....

Hans

Richard Gooch writes:
> Hans Reiser writes:
> >
> > Nothing I have said makes it mandatory that you choose to do an open
> > or a create on the directory, or that you use any filters.
>
> I'm glad to hear that, but I don't understand how that would
> work. I've heard talk about automagically tarring up directories,
> accessing "default" files when opening a directory, and so on. So how
> do you make this user (per process) configurable?
>
> Especially if data filters/default opening/automagic tarring is put
> into the kernel/FS, how do you make that user configurable?
>
> 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/

-
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/