0.3Operating systems (Windows, macOS, Linux)
The essentials in 30 seconds
- The OS is the software layer between hardware and applications: it manages memory, files, processes and peripherals.
- Windows = offices, macOS = creation, Linux = servers and cloud — each OS has its preferred ground.
- Concepts transfer: users, permissions, files, processes and updates exist on all three.
Running mini-case — Sofiane moves from Windows to the Linux server in Algiers
Sofiane, a support technician at the distribution SME in Algiers, is comfortable on Windows, the OS of the company's workstations. But when the SME's web server goes down, he discovers that the machine runs Linux — free, robust, driven from the command line. Rather than learning a third system from scratch, he looks for the common concepts: users and permissions, file system, processes, updates. He finds his bearings again. He notes the generalist's reflex: master Windows (the workstation), add Linux basics (servers/cloud), and practice in a virtual machine with no risk.
Standalone case for this section: it returns in the course, the diagram, the script and the 48h challenge of section 0.3.
1. What an operating system is for
The operating system (OS) is the software layer between the hardware and the applications. It manages memory, files, processes and peripherals, and offers programs a uniform way to use the machine. Without it, every application would have to talk directly to the hardware — unimaginable. Sofiane relies on this layer every time he works on a workstation or a server.
2. Three families, three grounds
Windows dominates business workstations. macOS is widespread in creative professions (and runs only on Apple hardware). Linux, free and robust, dominates on the server side and in the cloud. Sofiane learns to place each OS before assuming he does not know the machine.
3. Concepts that transfer
All three share the same big ideas: users and permissions, file system, processes, drivers, updates. Understanding these concepts on one OS lets you find them on the others — the mark of a good generalist is knowing how to move from one to another, like Sofiane from the Windows workstation to the Linux server.
🔎 Concrete example — 🔎 Concrete example — Why Linux on the server side?
Sofiane compares two contexts around the same need:
Everyday office workstation → often Windows
Web server / cloud service → very often Linux
→ same concepts (users, files, processes).Reading: a server values stability, efficiency, security and cost — strengths of Linux, free and manageable from the command line.
Lesson: even in a "Windows" company, you meet Linux behind the scenes (services, cloud).
Section vocabulary
- Operating system (OS)
- Software layer between hardware and applications; manages memory, files, processes, peripherals.
Simple example: Sofiane identifies the OS before working on a workstation.
What it is not: a simple office software.
Reflex: hardware ↔ applications → OS.
- Windows
- Microsoft's OS, standard on business workstations.
Simple example: Sofiane's SME workstations run Windows.
What it is not: the company's web server, often on Linux.
Reflex: business workstations → Windows.
- macOS
- Apple's OS, common in creation, on Apple hardware only.
Simple example: There Sofiane meets the partner agency's graphic designer.
What it is not: any generic desktop PC.
Reflex: creation + Apple hardware → macOS.
- Linux
- A family of free, robust OSes, dominant on servers and the cloud.
Simple example: The SME's web server that Sofiane diagnoses runs Linux.
What it is not: an OS reserved for office workstations.
Reflex: servers and cloud → Linux.
- Kernel
- The core of the OS that talks to the hardware and shares its resources.
Simple example: Sofiane understands that the kernel arbitrates access to resources.
What it is not: a business application installed above the OS.
Reflex: talk to the hardware → kernel.
In practice — In practice — Comparing three systems
- For Windows, macOS and Linux, write one sentence on their most common use, like Sofiane for his SME.
- On a machine, find where to see the OS version and the updates.
- Find the equivalent of "list running programs" (task manager, activity monitor, or a command).
- Note two concepts present on all three (users, permissions, files…).
Step-by-step script — transferring your bearings like Sofiane (5 min)
1) Name the OS you use most (often Windows on the workstation). 2) List the key concepts: users, permissions, files, processes, updates. 3) Open a Linux server or virtual machine and find these same concepts. 4) Note what changes (the interface, the commands) and what stays (the concepts).
A generalist benefits from moving between OSes by relying on the common concepts, not by relearning everything.
Copy-paste template — my OS map
Running thread: Sofiane, support technician — distribution SME in Algiers.
OS = layer between hardware and applications (memory, files, processes).
Windows → business workstations · macOS → creation · Linux → servers/cloud.
Common concepts: users, permissions, files, processes, updates.
Strategy: Windows first, then Linux basics in a virtual machine.Windows workstation
Sofiane solves daily the incidents of the SME's Windows workstations.
Linux server
Sofiane diagnoses the SME's web server, driven from the command line.
Transferred concepts
Sofiane finds users, permissions and files from one OS to another.
Virtual machine
Sofiane practices Linux in a VM, with no risk to production workstations.
✓ Best practices
- Master Windows (the workstation), then add Linux basics (servers/cloud).
- Look for the common concepts rather than learning three times.
- Practice in a virtual machine with no risk.
✗ Common pitfalls
- Believing yourself loyal to a single OS.
- Ignoring Linux "because we're on Windows".
- Confusing the interface (which changes) and the concepts (which stay).
Key takeaways
- The OS is the intermediary between hardware and applications.
- Windows = offices; macOS = creation; Linux = servers/cloud.
- The same concepts (users, files, processes) exist everywhere.
- A good generalist moves from one system to another.
48h challenge — apply it tomorrow
Like Sofiane, find a common concept across two OSes: state where the users and the permissions are on Windows, then on a Linux virtual machine. Note in one sentence what changes (interface, commands) and what stays identical.
- I can explain the role of an operating system.
- I place Windows, macOS and Linux according to their use.
- I can transfer the common concepts from one OS to another.
Frequently asked questions
Why is Linux so present on servers but little on desktops?
Servers value stability, efficiency, security and being free — strengths of Linux; the "desktop" experience matters less on a machine without a screen. That is also why the cloud runs massively on Linux.
Windows or Linux first?
Windows, because that is what you will support most in an SME like Sofiane's; then Linux basics early enough, to practice in a virtual machine.
What does an operating system do?