↓ Skip to main content
Anohba Jehad
  1. Posts/

Behind the Prompt

·624 words·3 mins
Shell POSIX Shell Programming
Table of Contents

If you’ve ever used a Linux terminal or written a script to automate tasks on a Unix-like system, you’ve already brushed up against the world of shell scripting. But there’s one term that often floats around with little explanation, the POSIX shell. What is it, and why does it matter?

What Is a Shell?
#

A shell is a program that provides a command-line interface (CLI) for users to interact with the operating system. There are many types of shells, including:

  • bash (Bourne Again Shell)
  • zsh (Z Shell)
  • fish (Friendly Interactive SHell)
  • sh (Bourne Shell)

What Is POSIX?
#

POSIX stands for Portable Operating System Interface. It’s a set of standards created by the IEEE to make Unix-like operating systems more compatible with each other.

POSIX defines a standard shell behavior. This means if you write a script using only POSIX-compliant features, it should work on any POSIX-compliant system, such as:

  • Linux
  • macOS
  • BSD systems
  • Many embedded systems

What Is the POSIX Shell?
#

The POSIX shell is a standardized shell specification (based on the original Bourne shell) that ensures scripts can run consistently across different Unix-like systems.

This doesn’t refer to a specific shell executable, but rather a set of rules and features that compliant shells must follow.

Popular shells like bash, dash, ksh, and zsh all can act as POSIX-compliant when invoked as sh.

Why Learn the POSIX Shell?
#

ReasonExplanation
PortabilityYour scripts will run on any POSIX-compliant system.
SimplicityPOSIX scripts are typically cleaner and less complex.
SpeedSome POSIX shells (like dash) are very fast, making them ideal for boot scripts.
InteroperabilityIdeal for system scripts, Dockerfiles, and CI/CD pipelines.

POSIX Shell vs Bash
#

FeaturePOSIX ShellBash
CompatibilityUniversal (POSIX systems)Mostly Linux, not POSIX-only
FeaturesMinimalRich, advanced
PortabilityHighModerate
Common usageSystem scripts, initUser scripts, interactive use

Tip: Stick to POSIX when writing system-level scripts or scripts meant to run anywhere.

Writing a POSIX Shell Script
#

Let’s start with a simple POSIX-compatible script.

Example: Hello World
#

#!/bin/sh
echo "Hello, POSIX world!"

Key POSIX Shell Features
#

1. Variables
#

name="Anohba"
echo "Hello, $name"

No spaces around =, or it will error!

2. Conditionals
#

if [ "$name" = "Anohba" ]; then
  echo "Welcome!"
fi

Use [ ] for conditions, with spaces around the brackets.

3. Loops
#

i=1
while [ "$i" -le 5 ]; do
  echo "Number: $i"
  i=$((i + 1))
done

4. Functions
#

greet() {
  echo "Hi, $1!"
}
greet "Anohba"

5. Command Substitution
#

today=$(date)
echo "Today is $today"

POSIX allows $(…) and backticks ..., but $(…) is recommended.

Avoid Non-POSIX Bashisms
#

Examples of features not POSIX-compliant:

  • [[ … ]] for conditions

  • (( … )) for arithmetic (use $(( … )) instead)

function name {} syntax

  • Arrays

Always test your scripts with sh, not bash, if you want to ensure compliance.

How to Check for POSIX Compliance
#

Use dash (a minimal POSIX shell)
#

dash myscript.sh

Use shellcheck
#

shellcheck --shell=sh myscript.sh

This will warn you about any non-POSIX features.

Real-World Use Cases
#

  • Docker entrypoint scripts

  • Init/system scripts in /etc/init.d

  • Cron jobs

  • Embedded systems with busybox

  • CI pipelines that run across many environments

Conclusion
#

Getting comfortable with the POSIX shell is like learning a new superpower. It might seem a little cryptic at first, but once it clicks, you’ll wonder how you ever worked without it. From writing quick scripts to automating entire workflows, it’s a tool that quietly powers much of the tech world—and it’s right at your fingertips.

At its heart, the shell isn’t about being flashy. It’s about doing things clearly, simply, and well.

“The Unix philosophy: Write programs that do one thing and do it well.”
— Doug McIlroy