Unix shell

The Unix shell operates as a command-line interpreter that reads user input, parses it into commands, and executes them via system calls. It provides built-in commands (e.g., cd, echo, export) and external program execution, with features like piping (|), redirection (>, <), and job control (background/foreground processes).¹ The shell also supports variables, wildcard expansion, command substitution, and control structures (if, for, while), making it a full scripting language. Its design emphasizes composability: small utilities can be chained to perform complex tasks, a philosophy rooted in Unix's modularity.²

The first Unix shell, the Thompson shell, was written by Ken Thompson in 1971 at Bell Labs, providing basic command execution and redirection but lacking scripting capabilities. In 1979, the Bourne shell (sh) by Stephen Bourne introduced variables, control flow, and scripting, becoming the standard for Unix V7.³ The C shell (csh) by Bill Joy added C-like syntax and interactive features like history and aliases, but its scripting was less robust. The Korn shell (ksh) by David Korn combined Bourne compatibility with csh's interactive features. Bash, created by Brian Fox in 1989 for the GNU Project, became the default on Linux and macOS, incorporating features from sh, csh, and ksh.⁴

Modern Unix shells include Bash, Zsh, Fish, and Dash, each with distinct strengths: Zsh offers advanced completion and theming, Fish emphasizes user-friendliness, and Dash is optimized for speed and POSIX compliance. The POSIX standard (IEEE 1003.1) defines a common shell language based on the Korn shell, ensuring portability across systems.⁵ Shells also differ in interactive features: command-line editing (readline), programmable completion, and prompt customization. The choice of shell affects both user experience and script portability, as scripts written for Bash may not run in POSIX-only environments like Dash.

Beyond common usage, shells have niche features: the here-document allows embedding multi-line input, and process substitution (<(command)) enables treating command output as a file. The trap command handles signals, enabling cleanup on exit. Shells also support coproc for background processes with bidirectional pipes. Historically, the rc shell (Plan 9) simplified syntax, influencing later designs. Security aspects include shellshock (2014), a vulnerability in Bash's function parsing, highlighting the shell's deep integration.⁶ Additionally, shells can be used as login shells, affecting environment setup, and the dot command sources scripts in the current context.

Bash

Bourne Again SHell, a widely used Unix shell and scripting language.

POSIX

Portable Operating System Interface, a family of standards for Unix-like systems.

Command substitution

Replacing a command's output with its text in a shell command.

Job control

Ability to manage multiple processes, including backgrounding and foregrounding.