Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!wb3ffv!ka3ovk!raysnec!shwake
From: shwake@raysnec.UUCP (Ray Shwake)
Newsgroups: comp.unix.i386
Subject: Re: Wanted: ksh for 386/ix
Message-ID: <39@raysnec.UUCP>
Date: 27 Aug 90 21:37:07 GMT
References: <28739@netnews.upenn.edu> <70400019@m.cs.uiuc.edu> <1598@sixhub.UUCP>
Organization: IRS/CI - Technical Solutions Branch
Lines: 16

davidsen@sixhub.UUCP (Wm E. Davidsen Jr) writes:

>  The AT&T versions doesn't work well on SCO UNIX. As a matter of fact
>the only way it works at all is to boot /bin/sh and then run (not exec)
>ksh. "This will be fixed in a future version which will include ksh."

	I can't speak about ksh-88, since I'm using ksh-i compiled under
ISC 2.0.2 (the SCO Xenix/386 compiler couldn't handle it.*) It's the default
shell for a number of non-root users. I had a lot of problem booting with
C-shell as root's shell, somewhat better results with Korn Shell. Reinstalled
with Bourne as root's shell.

	I suspect SCO's "fix" involves the underlying system (kernel, boot
routines, etc.) and not (just) ksh itself.

* Don't yet have SCO's UNIX SDS.