Conceptual, architectural explainers — how a subsystem actually works underneath.
How bhyve uses hardware virtualization extensions to run guest operating systems, and the moving parts behind a running virtual machine.
Every emulator has to answer the same question: how do you run code written for one processor on a completely different one? Two fundamentally different answers, and why most serious emulators eventually need both.
How Apple Silicon's secure boot chain differs from Intel Macs, and the stages both go through to reach loginwindow.
How eBPF lets sandboxed, verified programs run inside the kernel, and why that changed what's possible for tracing, networking, and security tooling.
How GEOM's graph of providers and consumers underlies partitioning, RAID, encryption, and disk labels on FreeBSD.
What SIP protects, how it's enforced below the level of the root user, and the legitimate reasons to disable it temporarily.
Haiku's driver model inherits BeOS's modular, hot-pluggable design — but as a much smaller, community-driven project, its hardware support has real, practical limits worth understanding upfront.
How the VFS layer lets ext4, XFS, Btrfs, NFS, and procfs all answer to the same read/write/open calls.
Haiku runs on POSIX-like conventions and supports plenty of Unix software, but underneath that compatibility layer, it isn't descended from Unix at all — its kernel, API, and core assumptions come from somewhere else entirely.
A stage-by-stage walkthrough of how a FreeBSD machine goes from power-on to a login prompt, and where to intervene at each step.