Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!hoptoad!gnu
From: gnu@hoptoad.uucp (John Gilmore)
Newsgroups: comp.unix.wizards
Subject: ksh incompatabilities with sh?
Message-ID: <4627@hoptoad.uucp>
Date: 23 May 88 00:49:22 GMT
References: <2599@usceast.UUCP> <2601@usceast.UUCP> <4402@vdsvax.steinmetz.ge.com> <53764@sun.uucp>
Organization: Grasshopper Group in San Francisco
Lines: 15

> > 	(okay - you could rename ksh to sh)

guy@gorodish.Sun.COM (Guy Harris) wrote:
> Well, no, you really can't, not always.  There are supposedly a few real live
> incompatibilities that may break some scripts.

I have heard this too, over the years, and would like real
documentation on what's wrong.  Are there gross bugs in "sh" that ksh
is too polite to perpetuate, but which users depend upon?  It would
seem the best course to fix the ksh to match the sh in all respects,
rename it to /bin/sh, and throw away the old sh.  I thought that was
the original idea; what happened?
-- 
John Gilmore  {sun,pacbell,uunet,pyramid,ihnp4}!hoptoad!gnu        gnu@toad.com
"Use the Source, Luke...."