Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!ctnews!pyramid!prls!philabs!micomvax!musocs!mcgill-vision!mouse
From: mouse@mcgill-vision.UUCP (der Mouse)
Newsgroups: comp.unix.wizards
Subject: Re: symbolic links are a botch
Message-ID: <832@mcgill-vision.UUCP>
Date: Sat, 27-Jun-87 21:34:46 EDT
Article-I.D.: mcgill-v.832
Posted: Sat Jun 27 21:34:46 1987
Date-Received: Fri, 3-Jul-87 04:58:54 EDT
References: <7879@brl-adm.ARPA> <2211@bunker.UUCP> <2676@ulysses.homer.nj.att.com> <2680@ulysses.homer.nj.att.com>
Organization: McGill University, Montreal
Lines: 16

In article <2680@ulysses.homer.nj.att.com>, ekrell@hector..UUCP (Eduardo Krell) writes:
[ incidentally Eduardo, I suggest you get on your netnews admins to get
  rid of the extra . in that "..UUCP". ]
> I don't know the answer [to the Right Way to handle symlinks] but I
> certainly like the idea of "cd a/b; cd .." being equivalent to "cd a"
> whether "a" is a mount point, RFS mount point or a symbolic link.

It's not the symlinkness of a that matters but that of b.  I agree,
it's a nice idea, but it sounds to me more like a feature of cd than of
symlinks.  I've yet to hear a cohesive explanation of how symlinks
would work that includes this feature as a side effect, that is, in a
way that doesn't require special-casing cd.

					der Mouse

				(mouse@mcgill-vision.uucp)