Operating Systems · Lectures 1 to 8
Learn OS by doing.Read a lecture, run the idea,get marked on it.
Your eight lectures rewritten as clear notes with every worked example, plus simulators and quizzes so you can check you actually understood before the exam does.
$
Start here
New here? Read Lecture 1, then take its quiz.
Each lecture takes 20 to 75 minutes. Mark it done at the bottom, take the quiz, then open its lab. Your progress is saved in this browser.
The lectures
Eight lectures, in the order they were taught.
Each one has notes, diagrams, worked examples, a quiz, and a lab where there is something to simulate.
System structures
Introduction to Operating Systems
What an operating system is, how the hardware underneath it is organised, why the OS runs in two modes, and the five classic types of OS with their trade-offs.
System Calls and Interrupts
How a user program asks the kernel for help through system calls, the five categories of calls with their Windows and Unix names, and how hardware and software interrupts pull the CPU into the OS.
OS Design, Implementation and Structures
How you decide what an OS should be (user vs system goals, policy vs mechanism), the five ways to arrange a kernel from MS-DOS to loadable modules, and the six kinds of system programs that live on top.
Process management
Processes and Operations on Processes
What turns a program on disk into a running process, how its memory and state are organised, what the PCB stores, and the UNIX lifecycle of fork, exec, wait and exit, including zombies and orphans.
Process Scheduling
How the OS keeps the CPU busy: the queues a process moves through, the three schedulers that move it, and the cost of every context switch.
CPU Scheduling
Every CPU scheduling algorithm on the syllabus, each with the slide's worked example reproduced number by number: FCFS, SJF, SRTF, priority, round robin, multilevel queues, and multiprocessor scheduling.
Threads
What a thread is, what it shares and what it owns, why threads beat processes for many jobs, and how user threads map onto kernel threads in the many-to-one, one-to-one, many-to-many, and two-level models.
Practice
Reading is not enough. Run it.
Every lab starts with a three-step guide and a suggestion for what to try first, so you are never staring at an empty control panel.
Scheduling simulator
Watch FCFS, SJF, SRTF, priority and round robin build a Gantt chart, then get marked on random problems.
Openfork() terminal
Run C programs with fork, exec and wait in the browser. See every process and count them.
OpenDeadlock lab
Step through the Banker's algorithm and find cycles in a resource-allocation graph.
OpenOS shell
Type man deadlock, sched, or quiz. A friendly fake terminal for quick revision.
OpenRead
One lecture at a time. Notes, pictures, worked numbers, predict-the-output cards.
Run
Open the lab linked from that lecture and play until the behaviour feels obvious.
Get marked
Take the lecture quiz, then exam mode across lectures. Wrong answers come with explanations.