The Korn Shell

A.3 The Korn Shell

One of the first major alternatives to the "traditional" shells , Bourne and C, was the Korn shell, publicly released in 1986 as part of AT&T's "Experimental Toolchest." The Korn shell was written by David Korn at AT&T. The first version was unsupported, but eventually UNIX System Laboratories (USL) decided to give it support when they released it with their version of UNIX (System V Release 4) in 1989. The November 1988 Korn shell is the most widely used version of this shell.

The 1988 release is not fully POSIX-compliant ”less so than bash . The latest release (1993) has brought the Korn shell into better compliance as well as providing more features and streamlining existing features.

Unlike bash , the Korn shell is a commercial product; the source code is not available and you have to purchase the executable (which is usually bundled with the other utilities on most commercial versions of UNIX).

The 1988 Korn shell and bash share many features, but there are some important differences in the Korn shell:

·                 Functions are more like separate entities than part of the invoking shell (traps and options are not shared with the invoking shell).

·                 Coroutines are supported. Two processes can communicate with one another by using the print and read commands.

·                 The command print replaces echo . print can have a file descriptor specified and can be used to communicate with coroutines.

·                 Function autoloading is supported. Functions are read into memory only when they are called.

·                 String conditional tests have a new syntax of the form [[...]] .

·                 There is an additional "fake" signal, ERR. This signal is sent when a script or function exits with a non-zero status.

·                 One-dimensional arrays are supported, although they are limited to a maximum size of 1024 elements.

·                 Filename generation capabilities are substantially increased by expanding on pattern matching and including regular expression operators.

·                 The history list is kept in a file rather than in memory. This allows concurrent instantiations of the shell to access the same history list, a possible advantage in certain circumstances.

·                 There is no default startup file. If the environment variable ENV is not defined, nothing is read.

·                 The type command is replaced with the more restrictive whence .

·                 The primary prompt string ( PS1 ) doesn't allow escaped commands.

·                 There are no built-in equivalents to builtin , command , and enable .

·                 There is no provision for key bindings and no direct equivalent to readline .

·                 There are no built-in equivalents to pushd , popd , and dirs . They have to be defined as functions if you want them.

·                 The history substitution mechanism is not supported.

·                 Brace expansion is not supported in the default configuration, but is a compile-time option.

·                 ! is not a keyword.

·                 Prompt strings don't allow backslash-escaped special characters .

·                 There is no provision for online help.

·                 Many of the bash environment variables don't exist, notably:

Similar products

• 

  Big Java: Compatible with Java 5, 6 and 7

• 

  Classic Shell Scripting

• 

  Bash Cookbook: Solutions and Examples for Bash Users (Cookbooks (O'Reilly))

• 

  sed & awk (2nd Edition)

Similar products