Am Freitag, den 27.08.2004, 02:21 +0400 schrieb Nikita Danilov: > > BTW, I can do a cd metas/metas/metas/metas/plugin/metas... I don't think > > this makes sense. :) > > Why? foo/metas is a file system object just like foo. It has owner, > permission bits, so access to its meta-data should be provided, and > uniform way to provide access to the file system object meta-data is to > have these little magic files inside metas directory, which is a file > system object just like metas. It has [EMAIL PROTECTED]@[EMAIL PROTECTED]@*** - Lisp > stack > overflow. RESET
Yes, of course. But who's going to need that? The meta files are there to describe regular unix files. They're just exported using a file system name space. I don't think we need metadata to describe metadata. Assuming someone adds a directory inside a file where user can add some attributes/streams/resource forks. As Linus said, they are just attributes, even if they seem to behave like normal files, they're not, they belong to the real file. Adding attributes to attributes to attributes? That would be like adding ACLS to ACLS. Hello the madness. ;-) There really should be a point where you can't recurse further. Assume there is a backup application that always tries to open every dentry it finds as directory and then recurse. Oops. :-)
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil