Messages in this thread | | | From | Nikita Danilov <> | Date | Mon, 4 Aug 2003 16:47:14 +0400 | Subject | Re: FS: hardlinks on directories |
| |
Stephan von Krawczynski writes: > Hello all, > > although it is very likely I am entering (again :-) an ancient discussion I > would like to ask why hardlinks on directories are not allowed/no supported fs > action these days. I can't think of a good reason for this, but can think of > many good reasons why one would like to have such a function, amongst those: > > - restructuring of the fs to meet different sorting criterias (kind of a > database view onto the fs) > - relinking of the fs for export to other hosts via nfs or the like (enhanced > security through artificially constructed, exported trees) > > Would a feature like that be seen as "big action" or rather small enhancement > to the fs-layer? > Are there any supporters for this feature out there?
Hard links on directories are hard to do in the UNIX file system model.
Where ".." should point? How to implement rmdir? You can think about UNIX unlink as some form of reference counter based garbage collector---when last (persistent) reference to the object is removed it is safe to recycle it. It is well-known that reference counting GC cannot cope with cyclical references. Usually this is not a problem for the file system because all cyclical references are very well known---they always involve "." and "..". But as one allows hard links on directories, file system is no longer tree, but generic directed graph and reference counting GC wouldn't work.
> > Regards, > Stephan
Nikita.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |