Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix
Subject: Re: Are links as useful as they could be?
Message-ID: <3739@umcp-cs.UUCP>
Date: Wed, 8-Oct-86 01:39:09 EDT
Article-I.D.: umcp-cs.3739
Posted: Wed Oct  8 01:39:09 1986
Date-Received: Wed, 8-Oct-86 20:12:04 EDT
References: <21127@rochester.ARPA> <65@its63b.ed.ac.uk>
Reply-To: chris@umcp-cs.UUCP (Chris Torek)
Distribution: net
Organization: University of Maryland, Dept. of Computer Sci.
Lines: 22

>In article <21127@rochester.ARPA> ken@rochester.UUCP (Comfy chair) writes:
>>There still is obviously a need for some kind of indirection mechanism.
>>I don't like symbolic links, there are some warts, like having to check
>>for looping, but I can't think of anything better.

In article <65@its63b.ed.ac.uk> simon@its63b.ed.ac.uk (Simon Brown) writes:
>The "check for looping" could be fixed for symbolic links by defining
>some primitive that converts a filename into the filename that it
>"really is" ....

All you have done is to move the check from namei() into this new
primitive.

If you are willing to expend large amounts of space, the symlink
loop checks can be made rigorous, e.g., by remembering each symlink
inode and requiring that no one appear twice.  The eight-links
limit seems to work well in practice, though, particularly since
symlinks slow name translation markedly.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu