fork, exec, and What Actually Happens When You Run a Command

When your shell runs `ls`, two distinct system calls happen in quick succession: `fork` clones the shell into two identical processes, then `exec` replaces the child's program with `ls`. This split is bizarre, beautiful, and the source of subtle bugs every developer eventually trips over -- from copy-on-write surprises to fork-after-thread disasters.