sh

Start an interactive shell

$ sh

$ sh [script.sh]

$ sh -c "[command1; command2]"

$ sh -x [script.sh]

$ sh -n [script.sh]

$ echo "echo hello" | sh

sh [-cefinvx] [script [argument...]]

sh is the POSIX-compliant command interpreter (shell). It provides the standard shell scripting environment and is guaranteed to be available on all Unix-like systems.
On many Linux systems, /bin/sh is a symbolic link to another shell (dash, bash, etc.) running in POSIX-compatibility mode. This provides both compatibility and performance benefits.
Shell scripts beginning with #!/bin/sh use POSIX sh, ensuring maximum portability. Scripts needing bash-specific features should use #!/bin/bash instead.
The shell reads commands from standard input, a file, or the -c argument. It supports variables, control flow (if, while, for, case), functions, pipelines, and I/O redirection.

-c string

Execute commands from string

Exit immediately if a command exits with non-zero status

Disable filename globbing (wildcard expansion)

Interactive shell

Read commands but do not execute (syntax check)

Print shell input lines as they are read

Print commands and arguments as they are executed

Treat unset variables as an error

Turn off option

Variables: NAME=value, $NAME, ${NAME}
Quoting: 'literal', "interpolated", \escape
Conditionals: if-then-elif-else-fi, case-esac
Loops: while-do-done, for-in-do-done, until-do-done
Functions: name() { commands; }
Tests: [ condition ], test condition
Arithmetic: $((expression))

POSIX sh lacks many bash features: arrays, [[ ]], brace expansion, process substitution, many string manipulations. Write portable scripts or explicitly require bash.
The -e option can cause unexpected exits. Commands in conditions (if, while) or with || / && don't trigger exit on failure.
Different systems link /bin/sh to different implementations (dash, bash, ksh). Test scripts on target systems or use explicit interpreters.

bash(1), dash(1), zsh(1), ksh(1), csh(1)