Bash

Infobox Software
name = Bash



caption = Screenshot of bash and sh sessions demonstrating some features
developer = Chet Ramey
latest release version = 3.2.39
latest release date = release date|2008|04|30
programming language = C
operating system = Cross-platform
platform = GNU
language = English, multilingual (gettext)
status = Active
genre = Unix shell
source model = Free software
license = GNU General Public License
website = [http://tiswww.case.edu/php/chet/bash/bashtop.html Home page]

Bash is a free software Unix shell written for the GNU Project. Its name is an acronym which stands for "Bourne-again shell". [ [http://www.ddj.com/cpp/184404693 C Programming] ] by Al Stevens, Dr. Dobb's Journal, July 1, 2001] The name is a pun on the name of the Bourne shell (sh), an early and important Unix shell written by Stephen Bourne and distributed with Version 7 Unix circa 1978, [ [http://www.ddj.com/architect/184415340 Fresh Faces] by Rosalyn Lum, Dr. Dobb's Journal, June 1, 2005] and the concept of being "born again". Bash was created in 1987 by Brian Fox. In 1990 Chet Ramey became the primary maintainer.cite web|first=Chet|last=Ramey|title=Bash - the GNU shell (Reflections and Lessons Learned)|url=http://www.wing.rug.nl/info/programs/bash/article.html#6|accessdate=2008-01-15]

Bash is the default shell on most GNU/Linux systems as well as on Mac OS X and it can be run on most Unix-like operating systems. It has also been ported to Microsoft Windows using the POSIX emulation provided by Cygwin, to MS-DOS by the DJGPP project and to Novell NetWare.

Features

The Bash command syntax is a superset of the Bourne shell command syntax. The vast majority of Bourne shell scripts can be executed by Bash without modification, with the exception of Bourne shell scripts referencing a Bourne special variable or those using builtin Bourne commands. Bash command syntax includes ideas drawn from the Korn shell (ksh) and the C shell (csh) such as command line editing, command history, the directory stack, the $RANDOM and $PPID variables, and POSIX command substitution syntax $(…). When used as an interactive command shell and pressing the tab key, Bash automatically uses command line completion to match partly typed program names, filenames and variable names.

Bash's syntax has many extensions which the Bourne shell lacks. Bash can perform integer calculations without spawning external processes, unlike the Bourne shell. Bash uses the ((…)) command and the $ […] variable syntax for this purpose. Bash syntax simplifies I/O redirection in ways that are not possible in the traditional Bourne shell. For example, Bash can redirect standard output (stdout) and standard error (stderr) at the same time using the &> operator. This is simpler to type than the Bourne shell equivalent 'command > file 2>&1'.

Bash supports here documents just as the Bourne shell always has. However, since version 2.05b Bash can redirect standard input (stdin) from a "here string" using the <<< operator.

Bash 3.0 supports in-process regular expression matching using a syntax reminiscent of Perl. [The syntax matches that shown on the [http://www.tin.org/bin/man.cgi?section=7&topic=regex regex(7)] man page.]

Brace expansion

Brace expansion is a feature, originating in csh, that allows arbitrary strings to be generated using a similar technique to filename expansion. However the generated names need not exist as files. The results of each expanded string are not sorted and left to right order is preserved:

# This is a bash specific feature echo a{p,c,d,b}e # ape ace ade abe

Brace expansions should not be used in portable shell scripts, because a traditional shell will not produce the same output:

# A traditional shell does not produce the same output echo a{p,c,d,b}e # a{p,c,d,b}e

Startup scripts

When Bash starts, it executes the commands in a variety of different scripts.

When Bash is invoked as an interactive login shell, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable.

When a login shell exits, Bash reads and executes commands from the file ~/.bash_logout, if it exists.

When an interactive shell that is not a login shell is started, Bash reads and executes commands from ~/.bashrc, if that file exists. This may be inhibited by using the --norc option. The --rcfile file option will force Bash to read and execute commands from file instead of ~/.bashrc.

Portability

Shell scripts written with Bash-specific features ("bashisms") will not function on a system using the Bourne shell or one of its replacements, unless bash is installed as a secondary shell and the script begins with "#!/bin/bash". This problem became particularly important when Ubuntu began to ship the Debian Almquist shell (dash) as the default scripting shell in October 2006, causing a wide variety of scripts to fail.

See also

* Comparison of command shells

References

External links

* [http://www.gnu.org/software/bash/bash.html Bash home page]
*
*
* [http://bashdb.sf.net/bashdb.html Bash Debugger]
* [http://linuxcommand.org/learning_the_shell.php Learning the shell] .
* [http://www.computerworld.com.au/index.php/id;1591223321;fp;16;fpid;1;pf;1 2008 interview with GNU Bash's maintainer, Chet Ramey]
* [http://bashscripts.org Bash Online Forum]