Stand-alone shell

Stand-alone shell (codice_1) is a Unix shell designed for use in recovering from certain types of system failures and errors.
The built-in commands of sash have all libraries linked statically, so unlike most shells on Linux, the standard UNIX commands do not rely on external libraries. For example, the copy command (cp) requires libc.so and ld-linux.so when built from GNU Core Utilities on Linux. If any of these libraries get corrupted, the coreutils cp command would not work; however, in sash, the built-in command, cp, would be unaffected.
In earlier times, most critical commands (including shells) in /sbin or even /bin were statically linked for this purpose, whereas in /usr/sbin and /usr/bin you would find the more feature-rich versions that were dynamically linked. This is not common anymore and as such, statically linked shells with built-in commands have become more important.
Sash has the following built-in commands:
The Sash shell has also been ported to work with Androidin a terminal-interface.
sash-plus-patches.
"sash-plus-patches" is a collection of patches for sash. The key features are the codice_32, codice_33, and codice_19 commands. However, these functions are available in newer versions of sash. These functions provide interfaces to the respective Linux system calls. They are especially useful when sash is used in an initial ramdisk ("initrd") environment. In addition, simple shell variable expansion support has been added; e.g., the variable "$(VAR)" is replaced by the content of the environment variable "VAR".
Some Linux distributions, such as Debian and Slackware (via SlackBuilds.org), have this available.