Part 7 of 8 · 2 min read
A short history
From batch jobs to phones
Think of a town that grew street by street. Old streets were not pulled down when new ones were added, so the map shows every age at once. Operating systems grew in the same way. The analogy stops in one place: a town keeps old streets, and an OS often replaces old ideas with better ones.
In plain words: Operating systems grew by adding ideas that worked and keeping them. The early ones were little more than libraries of common routines. Next came protection: a call into the OS became a special kind of call that changes the processor's privilege (page 2). Then came multiprogramming, and interrupts to handle devices (page 5). Time sharing let many people use one machine at once. Personal computers brought the OS to individual users, and today phones and servers run the same core ideas with a different balance of goals.
Early names for the OS were "supervisor" and "master control program". The name "operating system" caught on, since it describes a program in charge of making the system operate correctly and efficiently.
A tip for the rest of the course: nearly every later topic repeats the same pattern. A resource is limited, many programs want it, so the OS virtualises it, protects it and manages it with a policy on top of a mechanism.
Interview angle
Answer in your head first, then open it.
What is an operating system?
Software that manages hardware resources, gives programs a simple interface, and isolates programs from one another.
What does virtualisation mean here?
Presenting one physical resource as many virtual ones, such as one CPU as many.
Mechanism versus policy?
The mechanism is how, the policy is which.
Why multiprogramming?
To keep the CPU busy while programs wait for I/O.
Check yourself: 1. Which idea came after multiprogramming in the story above? 2. What pattern repeats in nearly every later topic? 3. Why did "operating system" win over "master control program"?
Words you will meet
| Word | Meaning |
|---|---|
| Process | A program in execution |
| System call | A request from a program to the OS |
| Resource | Something limited that programs share, such as the CPU |
| I/O | Input and output, such as disk and keyboard access |
| Degree of multiprogramming | The number of programs in memory at once |
| Protection | Keeping programs from harming each other or the OS |
Quick notes
- The processor repeats fetch, decode, execute. The OS adds sharing, protection and device access.
- Virtualisation turns one physical resource into many private, easier ones.
- Mechanism is how something is done. Policy is what choice to make. Keeping them apart lets either change.
- CPU use with n programs that each wait a share p of the time is 1 minus p to the power n.
- Design goals such as speed, protection and reliability pull against each other.
- Operating systems grew by keeping ideas that worked.