Operating System Fundamentals

An operating system (OS) is the master software that manages all the hardware and software on a computer. Think of it as the middle layer between you and the physical machine. When you click an icon, type a keyboard shortcut, or plug in a USB drive, the OS translates that action into commands the hardware understands. Without an OS, you would have to write raw machine code (binary 1s and 0s) just to move a mouse pointer.

The OS has four main jobs: managing hardware resources (CPU, memory, storage, input/output devices), running applications, providing a user interface (so you can interact with the computer), and enforcing security (user accounts, permissions, and file protection). Let's break each one down.

Hardware resource management is the most critical job. The CPU (Central Processing Unit) is like a chef — it can only cook one dish at a time, but it switches between tasks so fast that it seems to cook everything simultaneously. The OS schedules these CPU tasks, deciding which application gets the CPU's attention now, for how long, and in what order. This is called process scheduling. Similarly, the OS manages RAM (Random Access Memory) — the short-term memory where active programs live. If you open too many browser tabs, the OS might move some data from RAM to the hard drive (a technique called virtual memory) to keep the system from crashing.

Running applications is what most people see: the OS provides a standard way for programmers to create software. Every app on your phone or laptop talks to the OS through something called an API (Application Programming Interface). When a video game wants to show a 3D image, it sends a request to the OS, which then talks to the graphics card driver. The driver is a small piece of software that translates the OS's request into a language the specific hardware model understands. Different hardware vendors (like NVIDIA or Intel) provide their own drivers, but the OS handles the bridge.

The user interface (UI) is what you directly interact with. Two main types exist:

Most modern operating systems support both, but the balance differs. Windows heavily promotes GUI, while Linux systems are often controlled by CLI in server environments.

Security and user accounts are another core OS function. The OS enforces that only authorised people can access certain files or settings. It does this through user accounts. A standard user account can run applications and change personal settings, but cannot install system-wide software or modify core system files. An administrator account can do anything. The OS also manages file permissions — who can read, write, or execute a specific file. For example, on a company laptop, only employees in the IT department might have permission to install new software.

Now, let's talk about the ecosystem around an OS. Different devices use different operating systems. Personal computers (PCs) typically run one of these:

Mobile devices use different operating systems:

In cloud computing and servers, you often encounter specialised operating systems. Server versions of Windows (like Windows Server) and Linux (like Red Hat Enterprise Linux or Ubuntu Server) are optimised for reliability, security, and running multiple services simultaneously. They might not have a GUI at all, because everything is managed through CLI or remote management tools.

Finally, the OS manages file systems — the structure for organising data on a disk. Common file systems include NTFS (used by Windows), APFS (used by macOS), and ext4 (used by Linux). Each has different strengths: NTFS supports large file sizes and permissions well; APFS is optimised for flash storage; ext4 is journaled (keeps a log to prevent data loss). The OS decides how to read and write to these file systems, so your Windows computer can't natively read a macOS drive without special software.

In summary, the operating system is the bridge between you and the hardware. It abstracts complexity, enforces rules, and enables millions of applications to run on devices ranging from smartwatches to supercomputers.

An IT support technician at a mid-sized company receives a ticket: 'The sales department printer is not working. User tried to print from their Windows laptop, but nothing happens.' The technician first checks the obvious — is the printer plugged in? It is. Then they right-click the Start button and open Device Manager, a built-in Windows tool that shows all hardware components. They see a yellow exclamation mark next to the printer driver entry, indicating a driver conflict.

The technician uses the operating system's update mechanism — Windows Update — to search for a new driver. Windows recognises the printer model (a network-connected HP LaserJet) and downloads a signed driver from Microsoft's servers. The technician restarts the print spooler service (a background process that manages print jobs) via the Services console, another OS component. They then log into the local user account on the salesperson's laptop and test by printing a test page from Notepad. It works.

That same week, a different issue arises: a user on macOS cannot open a spreadsheet created in Excel for Windows. The sheet uses a feature called 'Power Query', which is not available in macOS Excel. The technician advises using the Mac's built-in compatibility layer — macOS can natively open many Windows file formats, but advanced features may fail. They suggest the user save the file in a generic format (.csv or .xlsx without advanced features), or use a cloud solution like Office 365 remotely. This illustrates how OS-specific application compatibility can cause real work problems.

Another scenario: a server running Linux Ubuntu Server suddenly stops responding to remote connections. The IT administrator connects via a local keyboard and monitor (out-of-band management). They check the system logs by typing 'journalctl -xe' in the terminal. They see a disk space warning: the /var/log directory (which stores system messages) is 100% full because an application has been logging errors excessively. Using commands like 'du -sh /var/log/' (check directory size) and 'rm' (remove old log files), the admin frees up space. They then configure log rotation using 'logrotate', a Linux utility, to prevent recurrence. The OS—in this case, Linux—provides the tools (file system management, logging daemons, command-line utilities) to diagnose and fix the issue.

Finally, consider mobile device management. An employee loses their company-issued Android phone. The IT team uses an enterprise mobility management (EMM) tool that talks to Android's OS-level security APIs. They issue a remote wipe command. The OS receives the instruction, erases all user data, and factory resets the device — all because Android's OS architecture allows a remote administrator to trigger such actions. The same operation on an iOS device would require Apple's Find My service and a separate corporate configuration profile.

In every case, the operating system is the underlying platform that enables or blocks actions. IT professionals spend their days troubleshooting OS-level settings: services that won't start, drivers that conflict, permissions that block access, or boot configurations that fail. Understanding the OS's components — kernel, drivers, file system, services, user accounts, and security models — is not theoretical; it is the daily reality of keeping a business's technology running.