Reasoning Checkpoint
A design challenge, worked through in writing — no auto-grading, just a real attempt.
The Challenge
On Friday afternoon, John puts three support tickets in front of Anna. "Each one is a different job the operating system does. Tell me which part of the OS is involved, what's probably going on, and what you'd do — the right way."
Ticket 1: "My laptop freezes for minutes at a time. The fan is very loud." Ticket 2: "The app on the test server can't write its log file: Permission denied." Ticket 3: "The staging server is slow, and now saving any file fails with 'No space left on device'."
What Your Answer Needs
- For each ticket, name the OS job involved (process and CPU scheduling, users and permissions, memory, or file system and storage).
- For each ticket, explain the most likely cause in one or two sentences.
- For each ticket, list the first thing you'd check, and the tool or command you'd use.
- For each ticket, give the proper fix — and say what quick fix you would avoid, and why.
- Bonus: explain why the staging server might also feel slow when its RAM is nearly full, using virtual memory.
Stuck? A Few Hints
- Ticket 1 is very close to what happened to Anna in chapter 2.
- For ticket 2, look at the permission line and remember least privilege.
- For ticket 3, think about what a file system needs before it can save anything.
Before You Move On
These three tickets — frozen machine, permission denied, disk full — are some of the most common problems in all of IT. You'll meet them again on real servers. The habit to keep: name the OS job behind the symptom first, then fix the cause, not just the symptom. The full depth of operating systems is waiting in the dedicated Operating Systems course.