Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!cs.utexas.edu!swrinde!gem.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.unix.questions Subject: Re: Symlinks and .. Message-ID: <7090@ficc.uu.net> Date: 22 Nov 89 22:51:16 GMT References: <2755@munnari.oz.au> <12407@ulysses.homer.nj.att.com> <10168@alice.UUCP> Reply-To: peter@ficc.uu.net (Peter da Silva) Organization: Xenix Support, FICC Lines: 21 [ re: file systems treating .. as an operator rather than a link ] In article <10168@alice.UUCP> ark@alice.UUCP (Andrew Koenig) writes: > Suppose, for instance, that a directory has subdirectories foo > and bar and a file in foo says #include "../foo/x.h" . It is > important to be certain that the x.h included is really the one > in the foo subdirectory. This isn't a problem. "../foo/x.h" would work. It's the component *before* the ".." that gets eaten, not the one after it. Say you're in "/u/ark/bar", then "../foo/x.h" becomes "/u/ark/bar/../foo/x.h", which becomes "/u/ark/foo/x.h". The Amiga file system does this, by the way. I think it's more trouble than it's worth. -- `-_-' Peter da Silva . 'U` -------------- +1 713 274 5180. "The basic notion underlying USENET is the flame." -- Chuq Von Rospach, chuq@Apple.COM