Linux man-pages project ↗
System calls and interfaces
Shell tools, interfaces, and small programs that reward closer examination.
System calls and interfaces
Pipes transformed individual Unix utilities into components that could be combined interactively. An account of how a simple technical mechanism helped shape an enduring approach to software design.
C and Unix evolved together. Ritchie traces the progression from BCPL through B to C, explaining how early hardware constraints and the requirements of systems programming shaped the language.
One of AWK's creators, Alfred Aho, explains how the need for small data-processing programs led to a remarkably expressive language. Particularly interesting is the progression from pattern matching to AWK's pattern-action programming model.
AWK is more than a text-filtering utility: it is a compact, data-driven programming language. Records, patterns and actions combine to solve problems that might otherwise require substantially more code.
Sed illustrates the Unix idea of transforming data as it flows through a pipeline. Beyond simple substitutions, its pattern space and hold space provide a surprisingly capable model for scripted text transformations.
The pipe character looks simple, but its execution semantics deserve attention. This reference explains how commands are connected, when subshells are involved and how pipeline exit status works.
Rob Pike and Brian Kernighan's influential 1984 paper argues that a program's usefulness depends not just on its individual capabilities, but on how well it combines with other programs. Its criticism of unnecessary complexity remains relevant.
An interactive game for learning Vim commands and navigation.
A free, practical guide to text processing with Perl one-liners.