Don't Panic — Operating Systems Fundamentals

An operating system is the responsible adult between programs and hardware. Programs would like processor time, memory, files, network access, and devices. Giving each one the keys to the machine would end with somebody formatting the furniture. The operating system coordinates those requests so many programs can share finite resources without directly controlling the machine.

The first important idea is user mode and kernel mode. Applications normally work in user mode, where they have limited access. The kernel runs privileged operating-system code, which means it can schedule work, manage memory, coordinate input and output, and apply access rules. A protected request crosses a controlled interface, often a system call. That boundary is why an ordinary application failure is usually contained, while a kernel-mode failure can inconvenience everyone at once.

The second idea is the request path. Reading a file is not a private conversation between an application and a disk. The kernel checks the request, applies filesystem and permission rules, may use cached file data, and coordinates a driver when device work is needed. Completion returns through the same sort of machinery. Networks, displays, keyboards, and storage differ in detail, but they all ask the operating system to arrange the awkward bits.

The third idea is that a process is a resource boundary and a thread is an execution path inside it. The scheduler chooses runnable threads for processor time. Virtual memory maps program addresses to physical memory pages, giving processes isolation and useful caching without producing extra capacity from a nearby cupboard. When demand remains too high, memory pressure can still slow or stop work.

The surprise is that “the computer is slow” is not a diagnosis. It is a polite notice that a request may be waiting for CPU time, memory, a filesystem, a driver, a device, a network operation, or a permission check. Start by finding the affected process and the resource path. Changing configuration before measuring the constrained resource is how a small mystery acquires a sequel.

Read the Intro for the full map of components and boundaries. Use Slides when the request path needs a quick visual pass, and keep the Cheatsheet nearby for terms such as page cache, write-back, and least privilege. The Practice reference gives you read-only Linux observations, while the quiz checks whether the parts still line up after the terminology has attempted its usual administrative ceremony.