fork()'s copy-on-write duplication is why Apache's prefork MPM and PostgreSQL's process-per-connection model can spin up workers cheaply, and why a naive fork() in a multi-threaded program can deadlock (the classic post-fork mutex bug glibc's manual warns about). Building the PCB and generation tree by hand shows why chrome://process-internals and `pstree` display parent-child chains the way they do.