The layer in the middle
A computer is a collection of physical parts: a processor, memory, storage, a display, a keyboard, a network adapter. Applications, such as a web browser or a spreadsheet, are written to do useful things for people. The operating system sits between the two. It is the software that lets many different applications use the same hardware without each one needing to know the details of how that hardware works.
Without this layer, every program would need its own instructions for reading a disk, drawing on a screen or sending data over a network. Worse, two programs could try to use the same piece of hardware at the same moment and interfere with each other. The operating system solves both problems. It offers applications a consistent set of services and acts as a referee when they compete for resources.
These operating system basics apply to phones, laptops, servers, game consoles and many embedded devices. The details differ, but the jobs are largely the same.
The kernel
The core of an operating system is usually called the kernel. It runs with a high level of privilege and has direct control over the hardware. Everything else, including the programs you use every day, runs in a more restricted mode and has to ask the kernel for help when it needs something.
When an application wants to open a file, for example, it does not talk to the storage device directly. It makes a request to the kernel, which checks whether the request is allowed, carries it out and returns the result. This request mechanism is often called a system call. Because applications have to go through it, the kernel can enforce rules and protect the system from mistakes.
An operating system is more than the kernel. It typically also includes system libraries, background programs, a way to log in, tools for managing files and settings, and some form of user interface. People often say “the operating system” to mean this whole bundle.
What the operating system manages
Processes and the processor
A program on disk is just a file. When you start it, the operating system creates a process: a running instance with its own memory and state. A modern computer usually has dozens or hundreds of processes at once, but only a limited number of processor cores. The part of the operating system called the scheduler decides which process runs on which core, and for how long. It switches between them so quickly that everything seems to happen at the same time.
Memory
Memory (RAM) is fast but limited, and every process needs some. The operating system hands out memory, keeps track of who is using what, and normally prevents one process from reading or changing another’s memory. This isolation is one reason a crashing application does not usually bring down the whole computer. When memory runs short, the system may move less-used data to storage, which keeps things running but often makes them noticeably slower.
Storage and files
Raw storage is just a large number of blocks. The operating system organizes it so that people and programs can work with named files and folders instead. It also tracks who may read or change each item. The rules for how it does this are called file systems, and they differ between systems.
Devices and drivers
Printers, graphics cards, keyboards and network adapters all work differently. A driver is a small piece of software that knows how to talk to one kind of device and presents it to the operating system in a standard way. This is why you can often plug in a new mouse and have it simply work, and why a missing or faulty driver is a common cause of hardware problems.
Users and security
Most operating systems support multiple user accounts and decide what each may do. Ordinary accounts can run programs and change their own files, while administrative accounts can change the system itself. Giving people and programs only the permissions they need is the idea behind least privilege, and it limits the damage if an account or application is misused. Operating systems also help with data encryption features, firewalls and the checking of who is signing in, though how much protection you get depends on how the system is configured and kept up to date.
Ways people interact with an operating system
Most users meet the operating system through a graphical interface with windows, icons and menus. Behind that sits another way of working: typing text commands into a shell. Administrators often prefer this for repeated work, because commands can be saved and reused through shell scripting. Both approaches ask the same underlying system to do the work.
Where operating systems run
The same ideas appear in several settings:
- Desktops and laptops run a general-purpose system designed for one person at a time.
- Servers run a system tuned to provide services to many users over a network, often without a screen attached.
- Phones and tablets run systems built around touch, battery life and tightly controlled apps.
- Embedded devices, such as routers or appliances, run small specialized systems that users may never see directly.
Many organizations also run several operating systems at once on a single physical machine, which is possible because of virtualization, and use lightweight packaging such as software containers to share one operating system among separate applications. Even in cloud computing basics, the services people rent ultimately run on machines with operating systems underneath.
Keeping an operating system healthy
Because the operating system is the foundation, problems here affect everything above it. A few general habits help:
- Install updates. They often fix security weaknesses as well as bugs.
- Watch resource use. Consistently high processor, memory or disk use is a sign something needs attention, and basic system monitoring can show it before users complain.
- Control who has administrative rights. Fewer powerful accounts mean fewer ways for things to go wrong.
- Keep records. The operating system writes events to logs, which are valuable when tracing a fault.
- Back up important data. A sensible backup strategy protects you even when the system itself fails.
Why the basics matter
Knowing what an operating system does makes many everyday problems easier to reason about. A slow computer might be short on memory or busy with too many programs. An application that cannot save a file may lack permission. A device that does not respond may need a driver. None of these ideas requires deep technical knowledge, but they give you a map of where to look first, and that is often most of the battle when learning IT.