ENGINEERING REFERENCE · 15-YEAR ROADMAP

Operating System
Engineering Roadmap
A PRACTICAL 15-YEAR REFERENCE
From studying existing systems to designing your own — a
practical reference for engineers who intend to write kernels,
not just run them.

APPLICATIONS

SYSTEM LIBRARIES

KERNEL
process · memory · fs · net · drivers

HARDWARE
Contents
Seven chapters from the existing OS landscape to your own kernel.

01 The Operating System Landscape

02 Study Path Through Existing Operating Systems

03 Types of Operating Systems

04 Technologies Needed to Create a Modern OS

05 Physical Hardware Projects

06 The Ultimate Engineer Path

07 The Six Operating Systems Worth Mastering

2
 THE OPERATING SYSTEM LANDSCAPE

01
The Operating System Landscape
C H A P T E R O N E · T H E P L AY I N G F I E L D

Before building a new operating system, study the major OS families

that already exist. Knowing what has shipped — and why — is the
cheapest way to avoid rebuilding what already works.

APPLICATIONS

SYSTEM LIBRARIES

KERNEL

HARDWARE

T H E F O U R - L AY E R A R C H I T E C T U R E T H AT A L M O S T E V E R Y O S B U I L D S O N .

Catalog of Operating Systems

Reference list assembled from public sources. Categories are not mutually exclusive — Android, for
example, is both a Mobile OS and a Linux distribution.

C AT E G O R Y O P E R AT I N G S Y S T E M S

Desktop OS Windows 95, Windows 98, Windows XP, Windows Vista,

Windows 7, Windows 8, Windows 10, Windows 11

Linux Distributions Ubuntu, Debian, Fedora, Arch Linux, Linux Mint, Kali Linux,
Red Hat Enterprise Linux, openSUSE

Unix Systems AIX, HP-UX, Solaris

3
 THE OPERATING SYSTEM LANDSCAPE

BSD Systems FreeBSD, OpenBSD, NetBSD, DragonFly BSD

Apple OS macOS, iOS, iPadOS, watchOS, tvOS

Android Family Android, Android Go

Mobile OS (Historical) Symbian, BlackBerry OS, Windows Phone, Tizen, Sailfish OS

Real-Time OS (RTOS) FreeRTOS, QNX, VxWorks, Zephyr, ThreadX

Embedded OS Embedded Linux, Contiki, TinyOS

Server OS Windows Server, Red Hat Enterprise Linux, Ubuntu

Server, FreeBSD

Mainframe OS z/OS, z/VM

Research / Educational OS MINIX, Xv6, HelenOS, Haiku

Open-Source OS Projects Linux, FreeBSD, OpenBSD, ReactOS, SerenityOS

Experimental OS TempleOS, Redox OS, Fuchsia

Cloud / Container OS Flatcar Linux, Bottlerocket, Fedora CoreOS

Most engineers never touch more than a handful of these deeply. The real study list is shorter than the
catalog suggests — and that list is the subject of the next chapter.

4
 STUDY PATH THROUGH EXISTING OPERATING SYSTEMS

02
Study Path Through Existing
Operating Systems
C H A P T E R T W O · A T E N - S TA G E C L I M B

A staged sequence for moving from the command line of a 1980s

microcomputer into the kernel internals of a modern phone. Each
stage builds on the one before it.

The Ten Stages

01 DOS
Command line basics

02 Linux
Files, processes, permissions

03 Ubuntu / Debian
User-space and package management

04 Windows
GUI and desktop architecture

05 Android
Mobile OS architecture

5
 STUDY PATH THROUGH EXISTING OPERATING SYSTEMS

06 FreeBSD
Unix-like kernel design

07 MINIX
Microkernel concepts

08 ReactOS
Windows-compatible OS development

09 Fuchsia
Modern microkernel architecture

10 Linux Kernel
Professional OS engineering

These ten stages trace a path from a 1980s prompt-driven environment into the kernel internals of a
modern phone — the same path the professionals walk.

6
 TYPES OF OPERATING SYSTEMS

03
Types of Operating Systems
C H A P T E R T H R E E · C AT E G O R I E S O F S Y S T E M

OS are usually grouped by what they were designed to do. The

categories are stable in textbooks and slippery in practice — modern
systems blur several of them at once.

Ten Categories, Reference Examples

Batch OS
IBM Mainframe Systems

Time-Sharing OS
Unix, Linux

Distributed OS
Amoeba, Plan 9

Network OS
Windows Server, NetWare

Embedded OS
FreeRTOS, Zephyr

Mobile OS
Android, iOS

7
 TYPES OF OPERATING SYSTEMS

Real-Time OS
QNX, VxWorks

Desktop OS
Windows, macOS, Linux

Server OS
Linux Server, Windows Server

Cloud OS
CoreOS, Bottlerocket

The categories are not exclusive — modern systems blur several of these at once. Cloud OS,
for instance, runs on Servers and often inherits Real-Time scheduling primitives for container
latency budgets.

8
 TECHNOLOGIES NEEDED TO CREATE A MODERN OS

04
Technologies Needed to Create a
Modern OS
C H A P T E R F O U R · T H E K N O W L E D G E S TA C K

Nine areas that any working OS engineer touches, most of them

deeply. Use this chapter as a checklist of disciplines rather than a
syllabus — every row opens into many textbooks.

Nine Areas of Practice

Programming
C C++ Assembly Rust

Mathematics
Logic Discrete Mathematics

Hardware
CPU GPU Memory Storage

Electronics
Digital Logic Microprocessors

Networking
TCP/IP Routing

9
 TECHNOLOGIES NEEDED TO CREATE A MODERN OS

Security
Cryptography Access Control

Graphics
OpenGL Vulkan GUI Systems

File Systems
FAT32 NTFS ext4 APFS

Virtualization
Hypervisors Containers

Compilers
GCC LLVM

Every row above is a deeper sub-discipline — 'Security' alone spans cryptography, capability design,
side channels, and sandboxing. Build broad familiarity now; specialise later.

10
 PHYSICAL HARDWARE PROJECTS

05
Physical Hardware Projects
C H A P T E R F I V E · H A R D WA R E C L O S E TO T H E M E TA L

A staircase of physical projects, each one a forcing function for the

engineer to understand the hardware their OS runs on. The chapter
renders as Physical Hardware Projects — the canonical name;
informal shorthand sometimes calls this section "Hard Projects."

The Staircase

BEGINNER Assemble a PC

BEGINNER Install Linux

I N T E R M E D I AT E Arduino Projects

I N T E R M E D I AT E Raspberry Pi Computer

A D VA N C E D Build a Custom Keyboard

A D VA N C E D FPGA-Based CPU

EXPERT Design a Simple Computer

EXPERT Design a Custom Single-Board Computer

11
 PHYSICAL HARDWARE PROJECTS

MASTER Design Hardware + Operating System Together

The capstone — hardware and software meet at the boundary you yourself have drawn.

Hardware and software co-evolve — an OS without hardware to run on is a simulation, and hardware
without an OS is hot metal. The Master row is the moment they meet.

12
 THE ULTIMATE ENGINEER PATH

06
The Ultimate Engineer Path
CHAPTER SIX · A FIFTEEN-YEAR TIMELINE

A practical timeline. Each pair of years marks a milestone; the

milestones compound. The chapter is not a schedule — it is a
calibration curve.

Years and Goals

Years 1–2 Python + C + Linux

Years 3–4 Data Structures + Algorithms

Years 5–6 Computer Architecture + Assembly

Years 7–8 Operating System Theory

Years 9–10 Build Bootloader + Kernel

Years 11– Drivers + File System

12

Years 13– Networking + Security

14

Years 15+ Create Your Own Operating System

13
 THE ULTIMATE ENGINEER PATH

Year 15+ is where the road opens into invention. Everything before it is preparation.

14
 THE SIX OPERATING SYSTEMS WORTH MASTERING

07
The Six Operating Systems
Worth Mastering
CHAPTER SEVEN · A FOCUSED STUDY LIST

Six systems cover the territory. To design a new OS, you do not need to
read every kernel — you need to read these well.

No engineer learns all operating systems completely. Most OS developers deeply

study six.

The Six

1 Linux
The production reference kernel — the place where most modern OS engineering is
teaching itself.

2 Windows
The dominant desktop API surface — required reading for any system that intends
to interoperate.

3 FreeBSD
A clean Unix-like with documented internals — the most legible production kernel
outside Linux.

15
 THE SIX OPERATING SYSTEMS WORTH MASTERING

4 MINIX
A microkernel teaching kernel — small enough to read end-to-end in a semester.

5 Android
A mobile stack on a Linux kernel — the most widespread runtime of any OS on Earth.

6 Fuchsia
A modern microkernel in production — the only recently-shipped kernel alternative
worth studying in depth.

These provide enough knowledge to design a completely new

operating system.

16