ARG_MAX| Shells | whatshell | portability | permissions | UUOC | ancient | - | ../Various | HOME
$@" | echo/printf | set -e | test | tty defs | tty chars |
)| IFS | using siginfo | nanosleep | line charset | locale
I created the list out of curiosity and from the viewpoint of history, portability and diversity; according to my own experiences, and with support from others (then as noted below). Additions are welcome.
See the traditional Bourne shell family concerning the various Bourne shells listed below.
See the end notes (bottom of page) for several system specific details.
Concerning the Korn shell variants ksh88 and ksh93, there's a
ksh end note.
The exact version of a ksh88 might not be sufficient, as some vendors have slightly modified their version.
A list of some ksh88 and ksh93 versions in the wilderness is on a separate page.
The default system shell, that is,
/bin/sh (not to confuse with default
login shells) on each flavour is emphasized in boldface.
pdksh v4.7 92/08/12
unametells a different version for both: "1.5.18(0.132/4/2) 2005-07-02 20:30")
|[ksh]|| About ksh versions on this page:
Here is a list of some ksh88 and ksh93 versions in the wilderness.
|[aix-ksh]|| AIX 5.3: The shell and its command and library environment becomes completely POSIX
compliant by setting |
|[domain-os]||DomainOS 10.4 offers two socalled universes: "bsd4.3" and "sys5.3". These provide bourne shells from 4.3BSD and SVR3, respectively.|
|[hp-posix]|| /bin/sh (at least) on HP-UX 11 comes with the undocumented flag "Q",
which disables reading of |
|[hp-ksh]|| Although the version string in the HP-UX ksh reports
"Version 11/16/88", it seems to be a ksh88c.
It's missing fixes from ksh88d; some examples:
|[irix-sh]||The Bourne shell on IRIX knows about "echo -n" and contains some SVR4.2 extensions, which are disabled, though; it seems to have been derived from between SVR4.0 and SVR4.2.|
|[irix-ksh]||ksh88f on IRIX 6.4 (and following versions), when called
as "sh" (and if $_XPG is not set to something greater 0), disables several
of its korn shell extensions, like |
|[mac-osx]||Strictly speaking, a shell must not be required on MAC OS X.
See developer.apple.com, "Responsibilities of Porting to Mac OS X":
"A Mac OS X user should never have to resort to the command line to perform any task in an application with a graphical user interface. This is especially important to remember since the BSD user environment may not even be installed on a users system. The libraries and kernel environment are of course there by default, but the tools may not be."
However, it is said, that the installation of shells de-facto can be safely assumed.
|[osf-sh]|| On OSF/1 you can decide at runtime which shell is forked off,
when calling |
|[sinix]||SINIX 5.20 offers three socalled universes: "ucb", "sie"(mens) and "xopen" (aka "att"). These provide shells from 4.2BSD, System III and SVR3, respectively. See some notes about the sinix universes if you are curious.|
|[ultrix-ksh]|| The version string in the Ultrix 4.0 ksh reports
"Version 11/16/88", and it's the first release,
because it's missing fixes from ksh88a, like
/usr/binis a universal convention on commercial unix flavours from "these days" (except for OpenServer and Unicos).
/usr/bin/shellis a rare exception.