Skip to content
Main menu
  • Main page
  • Discover
  • Unexpected connections
  • Topics
  • Random article
  • Search
Your library
  • Saved articles
  • Recent discoveries
  • Rabbit-hole trails
Topic areas
  • Computer Science
  • Mathematics
  • Physics
  • Engineering
  • Biology
  • Economics
  • Curiosities
WikiholeDeeper into Wikipedia
EnglishEN
  • Saved
  • History

  • Article text and media come live from Wikipedia via the official MediaWiki API and are available under the Creative Commons Attribution-ShareAlike 4.0 License; additional terms may apply. Each article links to its source and revision.
  • WikiHole is an independent project and is not affiliated with the Wikimedia Foundation.
  • How ranking works
  • All topics
  • Reading history
  • Random article
  • MediaWiki API

Unix shell

  • Article
  • Rabbit hole
  • Read
  • View history
Tools
Actions
  • Read
  • View history
General
  • Recent changes
  • Related articles
  • Random discovery
This article
Reading time
6 min
Topic
Computer Science
Quality
Start-class
Views
1.4k in 14 days
Last edited
27 Jul 2026
Print/export
  • Printable version
In other projects
  • Wikidata item
From Wikipedia, the free encyclopedia
Rabbit hole:
  1. Unix shell
Unix shell
Command-line interpreter for Unix operating system

A Unix shell is a shell that provides a command-line user interface for a Unix-like operating system. A Unix shell provides a command language that can be used either interactively or for writing a shell script.2 A user typically works within a Unix shell via a terminal emulator; however, direct access via serial hardware connections or a Secure Shell are common for server systems. Although use of a Unix shell is popular with some users, others prefer to use a graphical shell in a windowing system, such as those provided in desktop Linux distributions or macOS, instead of a command-line interface (CLI).

A user may have access to multiple Unix shells with one configured to run by default when the user logs in interactively. The default selection is typically stored in a user's profile (for example, in the local passwd file or in a distributed configuration system such as NIS or LDAP). A user may use other shells nested inside the default shell.

A Unix shell may provide many features including: variable definition and substitution, command substitution, filename wildcarding, stream piping, control flow structures (condition-testing and iteration), working directory context, and here document.

Loading the rest of the article…

Recent changes

Rabbit hole

Where Unix shell leads. Every connection below has a source: a link in this article, a shared Wikipedia category, or CirrusSearch text similarity. Articles already on your trail are left out.

Contents
  • (Top)
  • History
  • Configuration files
  • Other shells
  • See also
  • References
  • Recent changes
  • Rabbit hole
Contents
Contents7 sections
  • (Top)
  • History
  • Early shells
  • Bourne shell
  • C shell
  • Configuration files
  • Other shells
  • See also
  • References
  • Recent changes
  • Rabbit hole
Categories:
  • Unix shells
  • System administration

1,197 words · 22 references · revision 1366309205 · CC BY-SA 4.0

General
  • Recent changes
  • Related articles
  • Random discovery
This article
Reading time
6 min
Topic
Computer Science
Quality
Start-class
Views
1.4k in 14 days
Last edited
27 Jul 2026

Key concepts

  • C shell11
  • Unix-like2
  • MacOS2
  • Command substitution2
  • Control flow2
  • Here document2
  • Mac OS X Leopard1
  • Shell (computing)1
  • Command-line interface1
  • User interface1

The articles this one links to most, weighted towards the introduction.

Print/export
  • Printable version
In other projects
  • Wikidata item

History

Early shells

The first Unix shell was the Thompson shell, sh, written by Ken Thompson at Bell Labs and distributed with Versions 1 through 6 of Unix, from 1971 to 1975.3 Though rudimentary by modern standards, it introduced many of the basic features common to all later Unix shells, including piping, simple control structures using if and goto, and filename GLOBbing. Though not in current use, it is still available as part of some Ancient UNIX systems, such as Version 6 Unix.

It was modeled after the Multics shell, developed in 1965 by American software engineer Glenda Schroeder. Schroeder's Multics shell was itself modeled after the RUNCOM program Louis Pouzin showed to the Multics Team. The "rc" suffix on some Unix configuration files (e.g. ".bashrc" or ".vimrc"), is a remnant of the RUNCOM ancestry of Unix shells.14

The PWB shell or Mashey shell, sh, was an upward-compatible version of the Thompson shell, augmented by John Mashey and others and distributed with the Programmer's Workbench UNIX, circa 1975–1977. It focused on making shell programming practical, especially in large shared computing centers. It added shell variables (precursors of environment variables, including the search path mechanism that evolved into $PATH), user-executable shell scripts, and interrupt-handling. Control structures were extended from if/goto to if/then/else/endif, switch/breaksw/endsw, and while/end/break/continue. As shell programming became widespread, these external commands were incorporated into the shell itself for performance.

But the most widely distributed and influential of the early Unix shells were the Bourne shell and the C shell. Both shells have been used as the coding base and model for many derivative and work-alike shells with extended feature sets.5

Bourne shell

The Bourne shell, sh, was a new Unix shell by Stephen Bourne at Bell Labs.6 Distributed as the shell for UNIX Version 7 in 1979, it introduced the rest of the basic features considered common to all the later Unix shells, including here documents, command substitution, more generic variables and more extensive builtin control structures. The language, including the use of a reversed keyword to mark the end of a block, was influenced by ALGOL 68.7 Traditionally, the Bourne shell program name is sh and its path in the Unix file system hierarchy is /bin/sh. But a number of compatible work-alikes are also available with various improvements and additional features. On many systems, sh may be a symbolic link or hard link to one of these alternatives:

  • Almquist shell (ash): written as a BSD-licensed replacement for the Bourne Shell; often used in resource-constrained environments. The sh of FreeBSD, NetBSD (and their derivatives) are based on ash that has been enhanced to be POSIX conformant.
    • Busybox: a set of Unix utilities for small and embedded systems, which includes 2 shells: ash, a derivative of the Almquist shell; and hush, an independent implementation of a Bourne shell.
    • Debian Almquist shell (dash): a modern replacement for ash in Debian and Ubuntu
  • Bourne-Again shell (bash): written as part of the GNU Project to provide a superset of Bourne Shell functionality. This shell can be found installed and is the default interactive shell for users on most Linux systems; it provides both interactive mode (implemented by GNU Readline) or script-mode.
  • Korn shell (ksh): an enhanced version of the Bourne shell, written by David Korn based on the Bourne shell sources8 while working at Bell Labs
  • Public domain Korn shell (pdksh)
    • MirBSD Korn shell (mksh): a descendant of the OpenBSD /bin/ksh and pdksh, developed as part of

The POSIX standard specifies its standard shell as a strict subset of the Korn shell. From a user's perspective the Bourne shell was immediately recognized when active by its characteristic default command line prompt character, the dollar sign ($).

C shell

The C shell, csh, was modeled on the C programming language, including the control structures and the expression grammar. It was written by Bill Joy as a graduate student at University of California, Berkeley, and was widely distributed with BSD Unix.9

The C shell also introduced many features for interactive work, including the history and editing mechanisms, aliases, directory stacks, tilde notation, cdpath, job control and path hashing. On many systems, csh may be a symbolic link or hard link to TENEX C shell (tcsh), an improved version of Joy's original version. Although the interactive features of csh have been copied to most other shells, the language structure has not been widely copied. The only work-alike is Hamilton C shell, written by Nicole Hamilton, first distributed on OS/2 in 1988 and on Windows since 1992.10

Configuration files

Shells read configuration files in various circumstances. These files usually contain commands for the shell and are executed when loaded; they are usually used to set important variables used to find executables, like $PATH, and others that control the behavior and appearance of the shell. The table in this section shows the configuration files for popular shells.11

Configuration fileshkshcshtcshbashzsh
/etc/.loginloginlogin
/etc/csh.cshrcyesyes
/etc/csh.loginloginlogin
~/.tcshrcyes
~/.cshrcyesyesa

Other shells

Variations on the Unix shell concept that don't derive from Bourne shell or C shell include the following:15

  • es – A functional programming rc-compatible shell written in the mid-1990s.
  • Friendly interactive shell (fish) – First released in 2005.
  • PowerShell – An object-oriented shell developed originally for Windows OS and now available to macOS and Linux.
  • Qshell – A shell on the IBM i operating system based on POSIX and X/Open standards.
  • rc – The default shell on Plan 9 from Bell Labs and Version 10 Unix written by Tom Duff. Ports have been made to various Unix-like operating systems.
  • scsh – A Scheme Shell.
  • wish – A windowing shell for Tcl/Tk.

See also

  • Comparison of command shells
  • List of POSIX commands
  • Read–eval–print loop – Computer programming environment
  • Restricted shell
  • Shell account – User account on a remote server
  • Shell script – Script written for an operating system shell
  • Shell shoveling – Computer network security concept

References

  1. 1Tom Van Vleck (1995-02-05). "Unix and Multics". Multicians.org. Retrieved 2012-08-14.
  2. 2Bourne, Stephen R. (October 1983). "The Unix Shell". BYTE. p. 187. Retrieved 28 June 2026.
  3. 3"V6 Thompson Shell Port - History". V6shell.org. Retrieved 2012-08-14.
  4. 4Louis Pouzin (2000-11-25). "The Origin of the Shell". Multicians.org. Retrieved 2012-08-14.
  5. 5Nikolai Bezroukov (2015-08-13). "Introduction to the Unix shell history". Softpanorama. Archived from the original on 2022-06-08. Retrieved 2016-08-21.
  6. 6Bourne, Stephen (2009-03-05). "The A-Z of Programming Languages: Bourne shell, or sh" (Interview). Interviewed by Howard Dahdah. . Archived from on 2022-08-16. Retrieved 2022-08-16.
MirOS BSD
  • Z shell (zsh): a relatively modern shell that is partially backward compatible with bash. It's the default shell in Kali Linux since 2020.4 and macOS since 10.15 Catalina.
  • /etc/ksh.kshrcint.
    /etc/sh.shrcint.b
    $ENV (typically ~/.kshrc)12int.cdint.int.e
    ~/.loginloginlogin
    ~/.logoutloginlogin
    /etc/profileloginloginloginloginf
    ~/.profileloginloginlogingloginf
    ~/.bash_profileloging
    ~/.bash_loginloging
    ~/.bash_logoutlogin
    ~/.bashrcint.+n/login
    /etc/zshenvyes
    /etc/zprofilelogin
    /etc/zshrcint.
    /etc/zloginlogin
    /etc/zlogoutlogin
    ~/.zshenvyes
    ~/.zprofilelogin
    ~/.zshrcint.
    ~/.zloginlogin
    ~/.zlogoutlogin

    Explanation:

    • blank means a file is not read by a shell at all.
    • "yes" means a file is always read by a shell upon startup.
    • "login" means a file is read if the shell is a login shell.
    • "n/login" means a file is read if the shell is not a login shell.
    • "int." means a file is read if the shell is interactive.
    1. aonly if ~/.tcshrc not found
    2. bNewer versions of the Bourne Shell only
    3. cAvailable on systems that support the "User Portability Utilities option"; value of the variable must be an absolute path, and it is ignored "if the user's real and effective user IDs or real and effective group IDs are different."13
    4. d$ENV is $HOME/.shrc in newer versions of the Bourne Shell
    5. eSame behavior as sh, but only if invoked as sh (bash 2+) or, since bash 4.2, also if invoked explicitly in POSIX compatibility mode (with options --posix or -o posix).14
    6. fOnly in sh/ksh compatibility mode (when invoked as bash, sh, ksh)
    7. gThe first readable file in order of ~/.bash_profile, ~/.bash_login and ~/.profile; and only ~/.profile if invoked as sh or, as of at least Bash 4.2, if invoked explicitly in POSIX compatibility mode (with options --posix or -o posix)
    Computerworld
    the original
  • 7"Re: Late Bloomers Revisited". Retrieved 20 September 2014.
  • 8Korn, David G. (October 26, 1994), "ksh - An Extensible High Level Language", Proceedings of the USENIX 1994 Very High Level Languages Symposium, USENIX Association, retrieved February 5, 2015, “Instead of inventing a new script language, we built a form entry system by modifying the Bourne shell, adding built-in commands as necessary.”
  • 9Harley Hahn. "Unix/Linux Timeline". Harley Hahn's Guide to Unix and Linux.
  • 10"Hamilton C shell for Windows Release Notes 4.0". Retrieved 20 September 2014.
  • 11"Different UNIX Shells". unixnote.com. 2010. Archived from the original on 2016-04-03. Retrieved 2016-08-21.
  • 12Harley Hahn. "Exercises and Answers for Chapter 14... Using The Shell: Initialization Files". Harley Hahn's Guide to Unix and Linux.
  • 13"Shell Command Language". opengroup.org. Retrieved 15 June 2015.
  • 14"Bash Reference Manual: Bash Startup Files". gnu.org. Retrieved 15 June 2015.
  • 15"FreeBSD Ports: Shells". Freebsd.org. 2014-03-30. Archived from the original on 2021-01-12. Retrieved 2014-04-05.
  • Created
    26 Sept 2001
    History
    826 edits
    455 contributors
    No edits in the last 30 days
    Last edited
    27 Jul 2026

    826 revisions in total · 455 contributors

    1. 27 Jul 2026, 07:47 UTCGuy HarrisIf you're going to use "last, first", use separate last= and first= parameters.+15diff
    2. 28 Jun 2026, 17:11 UTCNeat93867Maintenance: expanded one citation for readability; added newlines and spaces; alphabetized fields; checked url for correctness; updated \access-date\; added an intra-link to \work\.+72diff
    3. 7 Jun 2026, 21:33 UTCTedickeymReverted 1 edit by ~2026-33760-26 (talk) to last revision by Guy Harris+2diff
    4. 7 Jun 2026, 20:46 UTCTemporary accountreverted§ Configuration files−2diff
    5. 12 Jan 2026, 23:19 UTCGuy Harris§ Bourne shell Put all the stuff about what the Korn shell is in the list entry for it. No need to link it a second time. Just call it the "Korn shell" - to what extent is it really call "KornShell" rather than "the Korn shell"? (Maybe KornShell is an official name, but, well, Google Ngram reports it's not as popular ss the original name - https://books.google.com/ngrams/graph?content=Korn+shell%2CKornShell&year_start=1980&year_end=2022&corpus=en&smoothing=3&case_insensitive=false)−3diff
    6. 12 Jan 2026, 23:08 UTCGuy Harris§ Early shells No reference, so it didn't happen. Give Version 6 Unix as an example of a system that has it (to emphasize how ancient it is).−53diff
    7. 12 Jan 2026, 23:03 UTCGuy HarrisUndid 2 revisions from 1325674729 until 1325674869 - MOS:BOLDTITLE+4diff
    8. 7 Jan 2026, 02:43 UTCCurlyquotemPunctuation+1diff

    View full revision history

    Created
    26 Sept 2001
    History
    826 edits
    455 contributors
    No edits in the last 30 days
    Last edited
    27 Jul 2026

    Related articles are unavailable right now.

    Wikipedia is rate limiting us right now. Try again in a minute.