Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.unix.amiga
Subject: Re: A3000UX - Born to run UNIX SVR4
Message-ID: <5692@auspex.auspex.com>
Date: 2 Feb 91 21:00:56 GMT
References: <581.27a97594@vger.nsu.edu>
Organization: Auspex Systems, Santa Clara
Lines: 23

>- Bourne Shell, Berkeley Shell, Korn Shell, Restricted Shell,
>  Remote Shell and Job Control Shell.

On the other hand, this is rather silly, althoguh maybe that's what you
want in a blurb.  The "Berkeley Shell" is presumably the C shell, or at
least that's what everybody *I* know calls it (if nobody else calls it
the "Berkeley Shell", perhaps it's *NOT* a good name to use in a
marketing blurb!).

The "Job Control Shell", the "Restricted Shell", and the "Bourne Shell"
are, as far as I know, all implemented by the *SAME* binary.  If you run
it as "sh", it's the Bourne shell; if you run it as "jsh", it's the "Job
Control Shell" (i.e., Bourne shell with job control); if you run it as
"/usr/lib/rsh", it's the "Restricted" shell (although I've heard it's
not quite as secure as some might think).

The "Remote Shell" is now what "rsh" is, the "Restricted Shell" being
sent off to "/usr/lib" so that BSDites won't have to think of the remote
shell as being "remsh" (as it is in some existing S5 systems).  I
wouldn't count it as an *additional* shell, though; i.e., the list of
shells given there really has only three shells in it: Bourne, C, and
Korn - or 2 1/2, if you think of the Korn shell as a Bourne shell
superset.