Operating Systems Foundations
Lesson Promise
By the end of this lesson, you will understand what an operating system is, what a process is, the five process states, and how processes differ from threads.
Narration Draft
Part 1 — What Is an OS? (3:00) An operating system is a resource manager and abstraction layer. Kernel vs user mode. The four roles: resource manager, abstraction layer, extended machine, file system.
Part 2 — What Is a Process? (4:00) A process is an executing program with its own memory and identity. Process Control Block (PID, state, registers, page tables). The five states.
Part 3 — Process Lifecycle Trace (4:00) Walk through fork() → ready queue → scheduled → running → I/O wait → ready → running → exit. Show context switches.
Part 4 — Process vs Thread (4:00) Memory isolation, creation cost, communication, failure boundaries. When to use each.
Visual Sequence
- OS layering: application → kernel → hardware
- Process Control Block fields (PID, state, registers, page tables)
- State transition diagram: New → Ready → Running → Waiting → Terminated
- Context switch: save state A, restore state B
- Process vs thread: separate address spaces vs shared memory
Companion Material
Related articles
What Is an Operating System?
An operating system is the resource manager and abstraction layer between hardware and applications, providing processes, memory, files, and devices.
System Calls: The User-Kernel Boundary
How applications request kernel services through system calls, the cost of mode switching, and common syscall patterns.
The Kernel Turns Shared Resources Into Program Abstractions
Understand how processes, virtual memory, scheduling, files, and system calls let programs share a machine.
More in Operating Systems
Operating Systems Advanced: Scheduling, Deadlocks, and Concurrency
Deep dive into CPU scheduling algorithms, deadlock prevention and detection, and advanced concurrency patterns for reliable systems.
DetailsOperating Systems Intermediate
Dive into system calls, concurrency with locks and semaphores, process management, and virtual memory.
DetailsWhat Happens During a read() System Call
A planned trace separates the userspace wrapper, kernel entry, descriptor lookup, cached data, I/O wait, and return value.
DetailsNew lessons by email
Get new articles and notes on the systems behind everyday software.
One technical dispatch per week. No noise.
Not started
Sign in to save your learning progress.