symlinks as directory entries vs. inodes

Chris Torek chris at umcp-cs.UUCP
Sun Nov 2 09:16:25 AEST 1986


In article <8551 at sun.uucp> guy at sun.UUCP writes:
>I presume they just decided the added benefits weren't worth the hassle.

What are the benefits supposed to be again?

Faster name translation?  The namei cache takes care of that.
Indeed, the extra code required to skip over the proposed extra
directory entry when scanning for other names might have more of
a slowing effect than any gain provided by having the contents of
the link at hand.

Less disk space used?  Perhaps; but not much, not unless you have
a large number of symlinks.

Fewer inodes used?  How often does one run out of inodes?  newfs is
very conservative about inode allocation.

All in all, I think writing the contents of the link through an
inode is cleaner.  It certainly helps keep namei, already a large
and ugly routine, from being larger and uglier.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris at umcp-cs		ARPA:	chris at mimsy.umd.edu



More information about the Comp.unix mailing list