Xref: utzoo comp.sys.att:2002 comp.unix.questions:4966 comp.unix.wizards:5996
Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!cornell!batcomputer!itsgw!steinmetz!dawn!stpeters
From: stpeters@dawn.steinmetz (Dick St.Peters)
Newsgroups: comp.sys.att,comp.unix.questions,comp.unix.wizards
Subject: Re: Non-standard shell and su.
Message-ID: <8389@steinmetz.steinmetz.UUCP>
Date: 6 Jan 88 22:53:52 GMT
References: <200@icus.UUCP> <264@ho7cad.ATT.COM>
Sender: root@steinmetz.steinmetz.UUCP
Reply-To: dawn!stpeters@steinmetz.UUCP (Dick St.Peters)
Organization: General Electric CRD, Schenectady, NY
Lines: 17

In article <264@ho7cad.ATT.COM> wjc@ho5cad.ATT.COM writes:
>Another ploy for getting  ksh for root  is to simply  link /bin/ksh on
>top of /bin/sh.  I've been running this way for quite a while  with no
>problems (3.5).

This can be very dangerous if any of your scripts expect to use
symlinks to reach remote parts of a filesystem:
	cd <symlink>
	cd ..
and you're back where you began, which is not how other shells behave
and is probably not what your script expected.

--
Dick St.Peters                        
GE Corporate R&D, Schenectady, NY
stpeters@ge-crd.arpa              
uunet!steinmetz!stpeters