What an operating system actually does

Updated: Oct 28, 2026

An operating system is the software that stands between hardware and every program you run. It decides which program gets the processor next, hands out memory and takes it back, turns a file name into blocks on a disk, delivers keystrokes to the right window and refuses to let one application read another’s data. Windows, macOS, Linux, Android and iOS differ in appearance and philosophy, but they all solve the same set of problems, and knowing what those problems are makes many everyday behaviours, from updates to permission prompts to “not responding” dialogs, easier to understand.

The kernel, drivers and processes

At the centre is the kernel, the privileged core that runs with full access to the hardware. Everything else, including the desktop, the browser and the file manager, runs as ordinary processes with restricted rights and asks the kernel for services through system calls. This separation is what lets the system survive a misbehaving application: the application can crash, but it cannot take the kernel down or scribble over another program’s memory.

The kernel’s main responsibilities:

• Process scheduling. A processor core executes one instruction stream at a time. The scheduler switches between processes and threads thousands of times a second, giving each a slice of time and priority. This is how dozens of programs appear to run simultaneously on a handful of cores.
• Memory management. Each process sees its own private address space. The kernel maps those virtual addresses onto physical RAM, moves rarely used pages to disk when memory runs short, and ensures no process can touch another’s pages.
• File systems. Disks store blocks; programs want named files in folders. The file system layer translates between them, tracks free space, enforces permissions and, on modern systems, journals changes so a power failure does not corrupt the structure.
• Device drivers. Every keyboard, network card, GPU and USB gadget speaks its own dialect. Drivers, loaded into or alongside the kernel, present them to the rest of the system through uniform interfaces.
• Security. User accounts, file permissions, sandboxes and capability checks all live here. When an application asks for the camera and the system shows a prompt, the kernel is enforcing the answer.

Above the kernel sits user space: system services (networking, printing, updates), the graphical shell, and the libraries applications link against. Most of what you see and interact with is user space; most of what keeps it honest is the kernel.

The main families

Windows dominates desktops through hardware and application compatibility, and its NT kernel underpins everything from laptops to Xbox. macOS and iOS share the Darwin kernel, combining a Unix foundation with Apple’s tightly integrated user space. Linux is a kernel around which distributions such as Ubuntu, Fedora and Debian assemble complete systems; it runs most servers, the majority of cloud infrastructure, and, as the base of Android, most phones. ChromeOS is Linux beneath a browser-centred shell. Embedded and real-time systems power routers, cars and appliances with far smaller kernels that prioritise predictable timing over features.

Everyday behaviour explained

• “Not responding” means the program stopped processing window messages, usually because it is stuck in a long operation. The kernel is fine; the application’s own main thread is busy.
• Updates need a restart when files the kernel or core services have loaded must be replaced; running code cannot be swapped in place safely.
• Permission prompts are the system inserting itself between an application and a sensitive resource, so the decision is yours rather than the developer’s.
• Slow with many tabs reflects memory pressure: the kernel is swapping pages to disk to keep everything resident.
• Safe mode starts with a minimal set of drivers and services, isolating problems caused by third-party additions.

Keeping your operating system healthy

• Install system updates promptly; the kernel and drivers are the highest-value targets for attackers.
• Use a standard account for daily work and an administrator account only when needed; this limits what a compromised application can change.
• Answer permission prompts deliberately. A flashlight app does not need contacts.
• Keep free disk space; both swapping and journaling need room to work.
• When something misbehaves, check what is using CPU, memory and disk in the system monitor before reinstalling anything.

Frequently asked questions

Is Linux an operating system or a kernel?

Strictly the kernel. A distribution combines it with a shell, libraries, package manager and applications into an operating system. In everyday speech “Linux” means the whole thing.

Why do the same programs not run on Windows and macOS?

Applications are compiled against a system’s specific calls, libraries and executable format. Cross-platform frameworks, web applications and compatibility layers such as Wine bridge the gap to varying degrees.

What is firmware, and how is it different?

Firmware (BIOS/UEFI) is the small program on the motherboard that initialises hardware and loads the operating system. Once the kernel is running, firmware mostly steps aside.

The operating system is the referee: it shares the hardware fairly and keeps every program inside its own lines.

In short: An operating system’s kernel schedules processors, manages memory, presents files and devices through uniform interfaces and enforces security, while user space provides everything you see. Most everyday quirks, from restarts to permission prompts to slowdowns, are the kernel doing exactly that job.