Subjects and lessons to explore.

Law

Computer Literacy · Foundations

Operating Systems

9 min read 5 practice questions
9 key termsSourcesReport an error
Want it in plain words first? Jump to Eli explains — the same idea, no jargon.
On this page 9 sections
  1. In 30 seconds
  2. Why this matters
  3. The college version
  4. Eli explains
  5. Worked example
  6. Key takeaway
  7. Quick check
  8. Study tools
  9. Sources & references

In 30 seconds

An operating system is the master software that runs a computer. It sits between your applications and the hardware, sharing the processor and memory among programs, storing and retrieving files, handling input and output, and enforcing who may do what. Its core, the , loads at startup and controls the hardware directly. Windows, macOS, and Linux run most computers; Android and iOS run most phones.

Why this matters

Almost everything you do on a computer or phone passes through its operating system, so understanding it demystifies the machine. Knowing that the OS schedules the processor, manages memory, and controls files explains why a computer slows down, why an app cannot reach a file, or why an update matters. In college and at work you will choose, configure, and troubleshoot systems across Windows, macOS, Linux, Android, and iOS; the concepts transfer even when the buttons differ. It is also the foundation for later topics in security, software, and files, because each of those depends on services the operating system provides.

The college version

What an operating system is

An is the system software that manages a computer's hardware and gives application programs a stable set of services to build on. NIST describes it as software that manages hardware resources and provides common services for programs. Without an OS, every application would have to speak directly to the processor, memory chips, disks, keyboard, screen, and network card, and no two programs could safely share them. The OS solves that by sitting in the middle: it is the intermediary between users and applications above it and the physical hardware below it. When you open a document, the application asks the OS for memory and for the file; the OS decides how to satisfy those requests and keeps other programs from interfering. Because it is loaded first and runs continuously, the OS is what turns a pile of hardware into a usable, general-purpose machine.

The kernel: the core that controls the hardware

At the center of the operating system is the kernel. It is among the first programs loaded at startup, right after the small bootloader, and it stays resident in memory the whole time the computer is on. The kernel has complete control over the hardware: it manages the processor and memory, and it reaches devices such as disks, network cards, and keyboards through small pieces of software called device drivers. When two programs want the same resource, the kernel arbitrates the conflict. To keep a misbehaving or malicious program from corrupting the whole system, the kernel runs in a protected, privileged mode, in memory that ordinary applications cannot touch (often called kernel space, as opposed to the user space where applications run). This separation is why one crashing app usually does not take the entire computer down with it. Not everything shipped with an OS is the kernel: the graphical interface, system utilities, and bundled apps sit on top of it, but the kernel is the part that actually governs the hardware.

What the operating system does day to day

It helps to name the OS's main jobs. : the OS decides which program runs on the CPU and for how long, switching between them so quickly that many appear to run at once. : it hands each program a region of memory, tracks what is in use, and keeps programs from reading or writing each other's memory. Storage and the : it organizes data on disks into files and folders and controls reading and writing them, so applications work with named files instead of raw disk locations. Input and output (I/O): it moves data between programs and devices such as the keyboard, mouse, display, printer, and network. Running and coordinating programs: it loads applications, gives them resources, and cleans up when they close. NIST summarizes this bundle as input/output control, resource scheduling, and data management. When a computer feels slow, it is often because these responsibilities, especially scheduling and memory, are stretched thin.

Security, user accounts, and access control

Because the OS controls the hardware and every file, it is also the natural place to enforce security. Operating systems support user accounts, each with its own identity and permissions, so that different people (or different programs acting on their behalf) can be granted or denied access to files, settings, and devices. The kernel's separation of user space from kernel space is itself a security boundary: application code cannot directly reach protected memory or hardware, and must ask the OS, which can check whether the request is allowed. This is how a standard user can be blocked from changing system settings, or one app can be prevented from reading another app's private data. Security here is about design and enforcement of these boundaries; it does not make any system automatically safe, and it works alongside practices like updates and strong authentication covered elsewhere.

How you interact with it: GUI and CLI

An operating system needs a way for people to give it instructions, and there are two broad styles. A is text-only: you type commands and the system prints text back. A is visual: you point at windows, icons, menus, and buttons with a mouse or a finger. Historically the GUI proved far more approachable for most people than the text-only command line, which is why phones and consumer computers lead with graphical interfaces. The CLI has not disappeared, though; it remains fast and precise for administrators, developers, and automation, and most desktop systems offer both. The important idea is that GUI and CLI are just two front doors to the same underlying operating system services.

Where operating systems run: desktop and mobile examples

The same core ideas appear across very different devices. On laptops and desktops, three families are common: Windows, macOS, and Linux. On phones and tablets, Android and iOS dominate. These are examples, not requirements, and each comes in many versions; Linux in particular is a Unix-like system created by Linus Torvalds and now runs on everything from servers to routers to phones (Android is built on the Linux kernel). Market share shifts over time: as of July 2026, StatCounter put Android at roughly 41% of worldwide usage across all platforms, Windows near 28%, and iOS near 20%, with macOS and Linux each in the low single digits. What matters for literacy is not memorizing shares but recognizing that whatever the brand, an operating system underneath is scheduling the processor, managing memory, handling files and I/O, and enforcing access.

Eli, the EliExplains learning guide

Eli explains

The same idea, in plain words

Explain it like I’m 10

A computer is really just parts: a processor that does the thinking, memory that holds what it is working on, storage that keeps files, and gadgets like the screen and keyboard. The operating system is the manager in charge of all of them. When you tap an app, the app does not touch the parts itself. It asks the operating system, and the OS decides who gets the processor next, where things go in memory, and which file to open. The busiest part of that manager is the kernel, which starts as soon as you turn the computer on and stays awake the whole time, making sure programs share the hardware without stepping on each other.

Picture it like this

Think of the operating system as the stage manager of a theater. The actors are the apps, the stage and lights and props are the hardware, and the audience is you. The actors never grab the lights themselves; they signal the stage manager, who decides who is on stage, when the lights change, and which prop comes out, so the whole show runs smoothly instead of everyone crowding the stage at once.

Where the picture stops working

A stage manager follows a fixed script and handles one show, while an operating system reacts moment to moment to whatever programs ask for and juggles many at the same time. And a stage manager is a person giving directions to other people; the OS is itself software that directly controls the machinery, with no separate crew underneath it.

Worked example

Suppose you are editing a photo while music plays and a large file downloads in the background, and the computer starts to lag. Trace it through the OS. All three programs want the same processor, so the scheduler is rapidly switching among them; with the photo editor demanding a lot of CPU, the others get thinner slices, and everything feels slower. All three also want memory: the editor holds a big image, and if the OS runs low on fast memory it starts shuffling data to slower storage, adding delay. When you hit Save, the editor does not write to the disk itself; it asks the OS, which routes the request through the file system and a device driver to the drive. If the file lived in another user's account, the OS would check permissions and could refuse. Every symptom you noticed maps to a specific operating-system responsibility: scheduling, memory management, file and I/O handling, and access control.

Key takeaway

The operating system is the software layer between applications and hardware: its kernel controls the machine while the OS schedules the processor, manages memory, handles files and input/output, and enforces access. Windows, macOS, Linux, Android, and iOS are examples of the same idea.

Quick check

3 questions here, of 5 in this lesson’s practice set. Answers stay hidden until you check.

Question 1 of 3foundational

Which statement best describes what an operating system is?

Choose an answer, then check it.
Question 2 of 3intermediate

Which statement about the kernel is correct?

Choose an answer, then check it.
Question 3 of 3intermediate

What is the difference between a graphical user interface (GUI) and a command-line interface (CLI)?

Choose an answer, then check it.
Practice all 5

Keep learning

Ready to build on this? Continue to the next lesson.

Practice this lesson
Study tools & related lessonsYou’ll learn to · Common mistakes · Easily confused · Key vocabulary · Related

You’ll learn to

  • Define an operating system as the system software that manages hardware and provides services to programs.
  • Explain the kernel's role as the core of the OS that controls hardware and runs in a protected mode.
  • Distinguish the main OS functions: processor scheduling, memory management, file/storage, input/output, and security.
  • Distinguish a graphical user interface (GUI) from a command-line interface (CLI).
  • Apply the OS-as-intermediary idea to explain everyday behavior such as slowdowns and permission errors.

Common mistakes

  • Thinking the operating system is just the desktop, wallpaper, or the apps you see.

    Those are surface features. The OS is the underlying software that manages the hardware and provides services; its core, the kernel, has no visible window at all.

  • Treating the kernel and the whole operating system as identical.

    The kernel is the core that controls the hardware, but the OS also includes the interface, system utilities, and bundled tools layered on top of the kernel.

  • Believing applications talk to the hardware directly.

    Applications ask the operating system, which decides how to use the CPU, memory, storage, and devices on their behalf and mediates conflicts.

  • Assuming a graphical interface (GUI) and a command line (CLI) are different operating systems.

    They are two ways of interacting with the same OS; many systems offer both, and both reach the same underlying services.

  • Concluding that because an OS enforces security it is automatically safe.

    The OS provides accounts, permissions, and isolation, but real security also depends on updates, strong authentication, and user choices.

Easily confused

Operating system vs. Application software

The OS manages the hardware and provides services; applications (like a browser or word processor) run on top of the OS and request those services.

Kernel vs. The rest of the operating system

The kernel directly controls hardware in protected mode; the interface, utilities, and bundled apps sit above it in user space.

GUI (graphical interface) vs. CLI (command-line interface)

A GUI is visual and point-based; a CLI is text and typed commands. Both are front ends to the same OS services.

Memory (RAM) vs. Storage (disk)

The OS manages both, but memory holds what programs are actively working on, while storage holds files persistently; the file system organizes storage.

Key vocabulary

Operating system (OS)
The system software that manages a computer's hardware and provides shared services that application programs rely on.
Kernel
The core of the operating system: loaded at startup, resident in memory, and in direct control of the hardware and resources.
Device driver
A piece of software that lets the operating system communicate with a specific hardware device, such as a printer or network card.
Processor scheduling
The OS's job of deciding which program runs on the CPU and for how long, so that many programs can share one processor.
Memory management
The OS's tracking and allocation of memory to programs, keeping each program's memory separate from the others.
File system
The way the operating system organizes stored data into named files and folders and controls reading and writing them.
User space and kernel space
The separation between the protected memory where the kernel runs and the ordinary memory where applications run.
Graphical user interface (GUI)
A visual way to control a computer using windows, icons, and pointers rather than typed text.
Command-line interface (CLI)
A text-only way to control a computer by typing commands and reading text responses.

Sources & references

  1. Operating System — Glossary — NIST Computer Security Resource Center (CSRC)
  2. Linux kernel README (Administration guide) — kernel.org — The Linux Kernel documentation
  3. Operating system — Wikipedia
  4. Kernel (operating system) — Wikipedia
  5. Operating System Market Share Worldwide — StatCounter GlobalStats

EliExplains lessons are original prose written from the open, credible references above. See Copyright & Licensing.

Researched 2026-08-19

Educational content only. It is not medical, legal or professional advice. Found an error? Tell us.