Engineer Atlas
OverviewLearnJourneysOS LabFinderRoadmapPracticeInterviewCheat SheetCompareConnections
OverviewLearnJourneysOS LabFinderRoadmapPracticeInterviewCheat SheetCompareConnections
Operating Systems
  • How Programs Run
  • Processes
  • Threads, Async & Event Loops
  • CPU Scheduling
  • System Calls & Kernel Mode
  • Stack & Heap
  • Virtual Memory & Paging
  • Files, File Systems & Descriptors
  • I/O
  • Concurrency, Synchronization & Deadlocks
  • Inter-Process Communication
  • Sockets
  • Containers & the OS
  • OS Internals Lab
  • OS Debugging & Capstone
OS + Networking
  • OS + Networking Together
OS/Learn/OS Internals Lab
Operating Systems

OS Internals Lab

A configurable OS simulator — cores, processes, threads, RAM, I/O, locks — and a panel of buttons to break it, then diagnose the failure.

The question this module answers · What happens to the scheduler, memory and I/O when I exhaust something?
The OS Simulator: Cores, Processes, RAM, I/O and Locks
▶ interactive

A configurable model of a kernel — set cores, processes, threads, RAM, I/O operations and locks, then watch the scheduler, context switches, memory, page faults, blocked tasks and lock contention respond; every number is an educational simulation of the mechanisms in this domain, not a measurement of any real machine.

Break the OS: Predict, Break, Diagnose
▶ interactive

Six buttons that push a simulated system past a limit — memory, locks, threads, disk, descriptors, the stack — each paired with what the real symptom looks like in logs and tools, and the one diagnostic question that separates the failure from its look-alikes.

Engineer Atlas
GitHub·LinkedIn