Every operating system concept in one video…

Fireship follows a computer from startup to shutdown to explain how an operating system shares hardware between programs. The walkthrough uses Linux and x86 examples; it is an introductory model, not a specification that applies unchanged to every operating system. This summary uses English auto-generated captions.

Key ideas

• Booting transfers control to the kernel. Firmware initializes enough hardware to find a bootloader, which loads the kernel into memory. In the x86 example, the kernel runs with hardware privileges while applications run at a restricted privilege level. Applications request protected operations through system calls rather than directly controlling the hardware. 01:02–03:56(opens in a new tab), 07:00–08:59(opens in a new tab)
• Virtual memory separates program addresses from physical RAM. The memory-management unit translates virtual addresses using page tables, and the translation lookaside buffer caches recent mappings. Separate process mappings support isolation. Fireship uses a missing page loaded from disk as his page-fault example; that example is not a complete account of all page faults. 02:02–04:59(opens in a new tab)
• Files and devices expose manageable interfaces to physical storage and hardware. In the inode-based filesystem explanation, an inode holds metadata and references to data, while directories map names to inode numbers. Drivers translate generic operations for particular devices; interrupts notify the CPU when hardware needs attention instead of requiring a program to check continuously. 03:56–07:00(opens in a new tab)
• Processes and threads divide running work. The scheduler shares CPU time among runnable work. Threads within a process share memory and file descriptors but have separate stacks and execution positions, making concurrency cheaper to organize while introducing shared-memory race risks. The video uses Linux's PID 1 and scheduler as examples. 07:00–10:41(opens in a new tab)
• Programs communicate through operating-system facilities. A pipe connects one process's output to another's input, illustrated with cat and grep. Sockets and message queues are other forms of inter-process communication. The shutdown example asks processes to exit before forcibly stopping those that remain and releasing system resources. 09:52–11:30(opens in a new tab)

Practical implications

• Editorial: Use the walkthrough to connect application behavior to the boundary involved: memory translation, a system call, CPU scheduling, or inter-process communication. It gives a vocabulary for further study rather than enough detail to implement or diagnose every mechanism.

Questions and limits

• Editorial: Several explanations are compressed. Do not generalize the inode example to every filesystem, assume every driver runs in kernel mode, or read privilege separation as the only security mechanism.
• The Railway segment is sponsorship; its deployment and cost claims are separate from the operating-system explanation. 03:56–06:02(opens in a new tab)

Full video: https://www.youtube.com/watch?v=MtxP2pyCvYA(opens in a new tab)