Setting Up a Raspberry Pi for Linux Real-Time Experiments
Preparing a headless Raspberry Pi 4 as a Linux laboratory for kernel, GPIO and real-time experiments.
Original articles and selected reading from the Unix world.
A collection of original UnixBits articles and carefully selected external technical resources.
Preparing a headless Raspberry Pi 4 as a Linux laboratory for kernel, GPIO and real-time experiments.
Inspecting kernel preemption on a Raspberry Pi 4 and distinguishing PREEMPT from PREEMPT_RT.
Control Raspberry Pi GPIO18 from Linux and verify HIGH and LOW output voltages using a digital multimeter.
Explore PID namespaces with unshare, compare process IDs from inside and outside, and discover why /proc matters.
Official kernel documentation
System calls and interfaces
A comprehensive BSD reference
Linux scheduling is an evolving design, not a settled algorithm. EEVDF uses virtual deadlines to balance fairness and responsiveness, offering an interesting comparison with the older Completely Fair Scheduler.
An exploration of the machinery behind virtual memory, address translation, page tables and page faults, including the interaction between hardware and the kernel.
A journey from user space into the kernel, revealing the architecture-specific machinery behind a seemingly simple system call. Older, but valuable for understanding the underlying mechanisms.
Containers are built from kernel mechanisms rather than a separate operating-system layer. This reference explains how namespaces isolate resources and how processes create, enter and inspect them.
A gateway into the kernel's internal programming interfaces, data structures and concurrency mechanisms. A useful reference map for exploring how Linux is implemented.
A look inside a complete BSD operating system, covering kernel initialization, virtual memory, locking, device drivers and jails. Particularly useful for comparing FreeBSD's implementation choices with those of Linux.
OpenBSD's distinctive approach to operating-system engineering: proactive code auditing, secure defaults and systematic removal of vulnerabilities. An interesting study of how engineering priorities shape an entire operating system.
NetBSD treats portability as an architectural discipline, separating machine-independent code from hardware-specific implementations. A demonstration of how careful abstraction supports radically different computer architectures.
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.
What distinguishes BSD from Linux beyond the kernel and licensing? A discussion of development organisation, source-tree integration and the BSD projects. Some comparisons also provide a useful historical perspective.
Dennis Ritchie looks back at Unix's strengths and weaknesses, including files, processes, the shell, reliability and security. Fascinating because it discusses design limitations from the perspective of someone who created the system.
The foundational paper by Ritchie and Thompson describing Unix's filesystem, processes and command interface. Remarkable for how many of its central ideas remain recognisable in modern Unix-like systems.
Ritchie's firsthand account of Unix's origins, from Multics to the development of filesystems, process control and pipes. Particularly interesting for the interplay between technical invention, available hardware and Bell Labs culture.
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.
A broader historical perspective on Unix's journey from Bell Labs research to universities, commercial implementations and standardisation. Useful for understanding how Unix developed into a family of related operating systems.
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.