Path: utzoo!attcan!utgpu!watserv1!watmath!uunet!wuarchive!psuvax1!rutgers!umn-d-ub!umn-cs!nis!sialis!rjg
From: rjg@sialis.mn.org (Robert J. Granvin)
Newsgroups: unix-pc.general
Subject: Re: second disk partitions on UNIXPC
Message-ID: <2075@sialis.mn.org>
Date: 8 Dec 89 03:34:53 GMT
References: <1049@icus.islp.ny.us> <12028@cbnews.ATT.COM> <1717@mtunb.ATT.COM>
Reply-To: rjg@sialis.mn.org (Robert J. Granvin)
Distribution: unix-pc
Organization: Dr. Ho Laboratory and Day Care Center
Lines: 29

In article <1717@mtunb.ATT.COM> jcm@mtunb.UUCP (John McMillan) writes:
>In article <12028@cbnews.ATT.COM> mvadh@cbnews.ATT.COM (andrew.d.hay,54242,wi,1d007,508 374 5484) writes:
>>what if you make ksh the standard SHELL for install, and make a .kshrc
>>file with alias -x ln=mv ?
>
>1) Replacing SH with KSH is a serious breach of sanity.
>	KSH is ALMOST a superset of SH -- but the differences are VERY
>	REAL.  It can waste hours or days for support people when folks
>	play this game.

Not the mention the ongoing babble several months ago...

ksh and sh differ in even the ways they handle errors.

If sh hits a line that blows off, the whole script blows off at that
point, and you stop.

If ksh hits a line that blows off, it feels the pain and loss, but
continues on happily through the script.

If your script _relies_ on the fact that it will fail if a line fails,
imagine the damage potential if it doesn't (And yes, there are many
like it).

-- 
________Robert J. Granvin________        INTERNET: rjg@sialis.mn.org
____National Computer Systems____          BITNET: rjg%sialis.mn.org@nic.mr.net
__National Information Services__            UUCP: ...amdahl!bungia!sialis!rjg
 "Insured against Aircraft, including self-propelled missiles and spacecraft."