Xref: utzoo comp.unix.i386:1657 comp.unix.xenix:8915
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!hp4nl!ctisbv!pim
From: pim@cti-software.nl (Pim Zandbergen)
Newsgroups: comp.unix.i386,comp.unix.xenix
Subject: Re: Shells (was: job control in 386/ix?)
Message-ID: <1647@ctisbv.cti-software.nl>
Date: 8 Dec 89 16:22:10 GMT
References: <3880@amelia.nas.nasa.gov> <1989Nov19.180741.8950@tolerant.com> <324@ubbs-nh.MV.COM> <1097@crpmks.UUCP>
Followup-To: comp.unix.i386
Organization: CTI Software BV, The Hague, the Netherlands
Lines: 33

garyb@crpmks.UUCP (Gary Blumenstein) writes:


>For those of you who are interested, Mortice Kern Systems, the makers of
>the MKS Toolkit for DOS has a Korn Shell available for both SCO and 
>ISC *NIX.

I have worked with both MKS's ksh and the Aspen Korn Shell.
I prefer the latter. the MKS korn shell is their own implementation
of the Korn Shell ; the Aspen is based on AT&T sources.

The MKS ksh is full of bugs. Lots of shell scripts in /bin and /usr/bin
fail with this product. MKS ksh cannot handle filenames of exactly
14 characters long, it thinks all filenames in directories are
null-terminated. I suspect they ported their DOS ksh to *nix
instead of the other way round.

I did not even bother to look for other bugs.

The Aspen Korn Shell works just fine for me.
It only displays a copyright message if it is invoked with -ksh
(ie login shell).

Note that you still need ksh source for job control, 
because currently these ksh's are not compiled with 
job control enabled.

Disclaimer: this is just my opinion.
-- 
Pim Zandbergen                           domain : pim@cti-software.nl
CTI Software BV                          uucp   : uunet!mcsun!hp4nl!ctisbv!pim
Laan Copes van Cattenburch 70            phone  : +31 70 3542302
2585 GD The Hague, The Netherlands       fax    : +31 70 3512837