Objective. Students will compare the architecture and purpose of Windows, macOS, and Linux, identifying kernel type, file-system defaults, and typical use cases for each.
This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
An operating system (OS) is the software layer that sits between hardware and the applications users run. It manages the CPU, memory, storage, and input/output devices so that programs do not have to control hardware directly. Every device a technician will touch in the field—desktop, laptop, server, or mobile—runs some form of OS. Understanding the architecture of major operating systems is a core competency tested on CompTIA A+ Core 2 and Cisco CCST.
The OS is divided into two logical zones.
Kernel space is where the kernel runs with full, direct access to hardware. The kernel handles memory management, process scheduling, device drivers, and system calls. Code running in kernel space can crash the entire system if it misbehaves, so only trusted OS components operate here.
User space is where ordinary applications run. Programs in user space must ask the kernel for resources through system calls. This separation protects the OS from poorly written or malicious applications. When a program crashes in user space, only that program stops—the OS keeps running.
Monolithic kernels bundle all core services—drivers, file-system management, networking—into a single large program running entirely in kernel space. Linux uses a monolithic kernel (with loadable modules). Performance is generally high because services communicate quickly inside the kernel.
Hybrid kernels move some services toward user space while keeping performance-critical parts in kernel space. Windows NT (the foundation of all modern Windows versions) and macOS both use hybrid kernels. The practical effect is a balance between performance and stability.
A 32-bit OS can address up to 4 GB of RAM. A 64-bit OS can address vastly more memory—current x86-64 processors support many terabytes of physical RAM in practice. Almost all modern hardware and software is 64-bit. A technician must still know 32-bit because:
When installing an OS, always match the OS architecture to the CPU and to the RAM installed in the machine.
Microsoft Windows is the dominant desktop OS in business environments. Modern versions are built on the Windows NT kernel (hybrid). Key technical details:
macOS (formerly OS X) is Apple's desktop OS, built on a UNIX foundation called Darwin, which itself uses a hybrid kernel called XNU.
Linux is an open-source OS kernel first released by Linus Torvalds in 1991. A complete OS is formed by combining the Linux kernel with a collection of utilities and a package manager—this combination is called a distribution (distro). Common distros include Ubuntu, Debian, Red Hat Enterprise Linux (RHEL), and CentOS.
| Feature | Windows | macOS | Linux |
|---|---|---|---|
| Kernel type | Hybrid (NT) | Hybrid (XNU) | Monolithic |
| Default file system | NTFS | APFS | ext4 |
| Settings store | Registry | .plist files | /etc text files |
| Source model | Proprietary | Proprietary | Open source |
| Hardware restriction | Broad x86-64 | Apple hardware only | Nearly any hardware |
OS work rarely involves physical hazards, but two points always apply in the lab and on the job.
1. Electrostatic discharge (ESD): When working inside a computer case during OS installation or troubleshooting, use an ESD wrist strap connected to a grounded surface. ESD can silently damage components.
2. Data safety before any OS task: Always confirm whether a backup exists before installing, reinstalling, or reconfiguring an OS. Data loss is the most common harm in OS work. Treat data protection as seriously as personal safety.
Knowing which OS is in use—and its architecture—is the first diagnostic step every time a ticket arrives.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.