Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!ulysses!hector!ekrell
From: ekrell@hector.UUCP (Eduardo Krell)
Newsgroups: comp.unix.wizards
Subject: Re: Non-standard shell and su.
Message-ID: <3333@ulysses.homer.nj.att.com>
Date: 8 Jan 88 14:18:16 GMT
References: <200@icus.UUCP> <264@ho7cad.ATT.COM> <8389@steinmetz.steinmetz.UUCP> <6974@brl-smoke.ARPA> <8400@steinmetz.steinmetz.UUCP>
Sender: daemon@ulysses.homer.nj.att.com
Reply-To: ekrell@hector (Eduardo Krell)
Organization: AT&T Bell Labs, Murray Hill
Lines: 27

In article <8400@steinmetz.steinmetz.UUCP> dawn!stpeters@steinmetz.UUCP (Dick St.Peters) writes:

>Problems likely to be more common than the one I originally cited are
>that under ksh
>	cd <symlink>
>	ls ../foo
>always gives "../foo not found".  Also,
>	if [ -f ../foo ]
>always yields false.

On the other hand, of course, a problem likely to be even more common
that these are that under csh or any other shell that treats symlinks
the way BSD does
	cd /usr/include/sys
	cd ..
doesn't put you in /usr/include (which is what I want all the time).
Also,
	ls ../*.h
doesn't list the header files in /usr/include (which is what I would
expect).

All this assumes /usr/include/sys is a symbolic link (which it is in
most BSD machines).
    
    Eduardo Krell                   AT&T Bell Laboratories, Murray Hill

    {ihnp4,ucbvax}!ulysses!ekrell