A Dialogue on the Book

Intro 💬 Dialogue OSTEP pp. 1–2 · ~5 min read

Three questions organise the whole book: who gets the processor, what breaks when things happen at once, and how data outlives the program that wrote it.

Why this matters

The three names are not chapter groupings, they are the questions each part is answering. If you cannot say which of the three a chapter belongs to, that is the signal to stop and reread the dialogue that opened the part.

The book opens the way it will open every major part: with a short conversation between a Professor and a Student. These dialogues are deliberate pauses — a chance to step outside the narrative and think about what’s coming.

Professor:Welcome to this book! It’s called Operating Systems in Three Easy Pieces, and I am here to teach you the things you need to know about operating systems. I am called “Professor”; who are you?
Student:Hi Professor! I am called “Student”, as you might have guessed. And I am here and ready to learn!
Student:Why is it called “Three Easy Pieces”?
Professor:There are these great lectures on Physics by Richard Feynman — some of the basics were summed up in a book called Six Easy Pieces. He was talking about Physics; we’re going to do Three Easy Pieces on the fine topic of Operating Systems. This is appropriate, as operating systems are about half as hard as physics.

The three pieces

Asked what the pieces actually are, the Professor names the three key ideas the entire book is organized around — and hints at the very concrete questions each one answers:

VirtualizationPart I · ch. 3–24Which program runs nexton the CPU?What happens when memoryoverloads in a virtualmemory system? (+ VMMs)ConcurrencyPart II · ch. 25–34Many things happeningat once: threads, locks,condition variables,semaphores — and the bugsuncontrolled timing breeds.PersistencePart III · ch. 35–51Managing information ondisks: devices, RAID, filesystems, journaling, SSDs —and distributed systems thatsurvive partial failure.The map for the whole book — each part opens and closes with a dialogue like this one.

The three easy pieces, with the concrete questions the Professor teases for each. The colors (blue / amber / emerald) mark these parts everywhere on this site.

Student:I have no idea what you’re talking about, really.
Professor:Good! That means you are in the right class.

How to learn this stuff

Student:What’s the best way to learn this stuff?
Professor:Each person needs to figure this out on their own, but here is what I would do: go to class to hear the professor introduce the material. At the end of every week, read these notes to help the ideas sink in; some time later (hint: before the exam!) read them again. And do the homeworks and projects — writing real code to solve real problems is the best way to put these ideas into action.

Tip: I do and I understand

The Student completes the Professor’s thought with the classic line “I hear and I forget. I see and I remember. I do and I understand.” — usually attributed to Confucius, though the Student (correctly!) credits the Confucian philosopher Xunzi as the better source. The book takes the advice seriously: nearly every chapter ends with homework simulators and projects, and this site links to them. On this site, “doing” also means playing with the interactive widgets — predict what a widget will show before you step it.

Why dialogues at all?

Student:What are these dialogues for? Isn’t this just supposed to be a book? Why not present the material directly?
Professor:It is sometimes useful to pull yourself outside of a narrative and think a bit; these dialogues are those times. So you and I are going to work together to make sense of all of these pretty complex ideas. Are you up for it?
Student:So we have to think? Well, I’m up for that. It’s not like I have much of a life outside of this book.
Professor:Me neither, sadly. So let’s get to work!

Ten more dialogues punctuate the book — one opening and one closing each of the three parts (plus one on distribution). When you hit one, treat it as the book intends: a moment to look up from the mechanism and ask what problem is actually being solved.

If you remember only three things

  • After this introduction, every chapter belongs to exactly one piece. Twenty-two chapters of virtualization, ten of concurrency, seventeen of persistence — and nothing at all sits outside the three.

  • Confusion at the start is the expected state. The Student’s “I have no idea what you’re talking about” earns “Good! That means you are in the right class” — the book setting expectations, not making a joke.

  • Doing is the part that sticks. Xunzi’s line is the book’s method rather than decoration: chapters close with something to run, and on this site the equivalent is guessing a widget’s output before letting it move.

Check yourself

1.What are the "three easy pieces" the book is organized around?

2.The title honors a famous set of physics lectures. Whose, and what does the Professor claim about the relative difficulty?

3.According to the dialogue, what is the single best way to make the ideas in this book stick?

3 questions