Almquist shell

Almquist shell
Developer(s) Kenneth Almquist
Initial release May 30, 1989 (1989-05-30)
Written in C
Operating system Unix-like
Type Unix shell
Website www.in-ulm.de/~mascheck/various/ash/

Almquist shell (also known as A Shell, ash and sh) is a lightweight Unix shell originally written by Kenneth Almquist in the late 1980s. Initially a clone of the System V.4 variant of the Bourne shell, it replaced the original Bourne shell in the BSD versions of Unix released in the early 1990s.

History, Versions and Impact

ash was first released via a posting to the comp.sources.unix Usenet news group, approved and moderated by Rich Salz on 30 May 1989. It was described as "a reimplementation of the System V shell [with] most features of that shell, plus some additions".[1]

The following is extracted from the ash package information from Slackware:

ash (Kenneth Almquist's ash shell)

A lightweight (92K) Bourne compatible shell. Great for machines with low memory, but does not provide all the extras of shells like bash, tcsh, and zsh. Runs most shell scripts compatible with the Bourne shell. Note that under Linux, most scripts seem to use at least some bash-specific syntax. The Slackware setup scripts are a notable exception, since ash is the shell used on the install disks. NetBSD and Ubuntu uses ash as its /bin/sh.

Fast, small, and virtually compatible with the POSIX standard's specification of the Unix shell, ash did not feature line editing or command history mechanisms, because Almquist felt that such functionality should be moved into the terminal driver. However, current variants support it.

Derivative versions of ash are installed as the default shell (/bin/sh) on FreeBSD, NetBSD, DragonFly BSD, MINIX, and in some Linux distributions. Android used ash until Android 4.0, at which point it switched to mksh[2].

dash: Ubuntu, Debian and POSIX compliance of Linux distributions

Debian Almquist shell (DASH)
Developer(s) Herbert Xu
Initial release July 15, 1997 (1997-07-15)
Written in C
Operating system Linux, Android
Type Unix shell
Website gondor.apana.org.au/~herbert/dash/

In 1997 Herbert Xu ported ash from NetBSD to Debian Linux. In September 2002, with release 0.4.1, this port was renamed to dash (Debian Almquist shell). Xu's main priorities are POSIX conformance and slim implementation.[3] Because of these two priorities it became very influential in the Linux world.

Slimness

Because of its slimness, Ubuntu decided to adopt the dash as the default /bin/sh[4][5] in 2006. The reason for using dash is faster shell script execution,[6] especially during startup of the operating system, compared to previous versions of Debian and Ubuntu that used bash for this purpose, although bash is still the default login shell for interactive use.[7] Dash became the default /bin/sh in Ubuntu starting with the 6.10 release in October 2006.[8] Dash replaced ash and became the default /bin/sh in Debian 6 (Squeeze).[9]

Dash implements neither support for Internationalization and localization nor support for multi-byte character encoding.

POSIX compliance

During the transition by Ubuntu, numerous scripts making use of bash-specific functionality (but not declaring it) were discovered.[10][11] The elements understood only by bash were called bashisms. Instead of stopping the process of migration to dash, they decided to make all the scripts comply with the POSIX standard. These altered scripts went upstream and, after a while, Debian also decided to adopt the dash as its default `/bin/sh`. The dash shell thus forced first Ubuntu and later on Debian to make their shell scripts POSIX compliant.

Embedded Linux

Ash is also fairly popular in embedded Linux systems; its code was incorporated into the BusyBox catch-all executable often employed in this area, and is used in distributions like DSLinux, Alpine Linux, Tiny Core Linux and Linux-based router firmware such as OpenWrt, Tomato and DD-WRT.

See also

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.