> In article <35E178D3.CBFC4174@flashnet.it>,
> "Sebastiano Tine'" <mb027878@flashnet.it> writes:
> > I have named it "Meta File Information". They consists in data
> > associated with the single file that user process can set and
> > read.
>
> > Does anyone ever thinked on it or implemented in some way ? I
> > need tips and suggestions on possible implementations.
>
> It is already implemented. It is called a "directory".
Yup... and IMO its a good way to do it.
MacOS files can fork into two - but why two? Is two really that
special in this case? And why can't these forks have forks?
NT has multiple forks, but those forks can't fork, etc.
I though about this one for a long time once when I was keen on the
metadata idea and decided directories are the most sane way of doing
this. If you want fancy stuff, then make a library that know how to
handle different bits in each directory, etc.
I think NeXT did something like this?
-cw
-
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.altern.org/andrebalsa/doc/lkml-faq.html