A Journey in Creating an Operating System Kernel — The 539kernel Book
mohammed-q-hussain, November 2022, 215 pages, free PDF from 539kernel.com, typeset in LaTeX.
Seven chapters that build 539kernel, a simple x86 32-bit kernel with multitasking, paging and its
own filesystem, from the boot sector upward. Source at github.com/MaaSTaaR/539kernel. Read locally
from the PDF with pypdf.
The spoke's first book. Every other source here is a repository, a PDF of questions, a study plan or a research paper; this is a single author writing continuous prose that happens to compile.
The shape of it
| Ch. | Subject |
|---|---|
| 1 | Bootloader — x86 assembly, NASM, GNU Make, QEMU/Bochs, BIOS services, hard-disk structure |
| 2 | x86 architecture — operating modes, segmentation in real and protected mode, the run-time stack and calling convention, interrupts and the IDT |
| 3 | "The Progenitor" — the starter, the first C kernel, remapping the PICs, writing ISRs |
| 4 | Process management — multiprogramming, scheduling, context, Task-State Segments (Version T) |
| 5 | Memory management — paging in theory, virtual memory, page directory and tables, dynamic allocation (Version G) |
| 6 | Filesystems — an ATA device driver, then 539filesystem designed and implemented (Version NE) |
| 7 | What's next — monolithic vs microkernel, and five research directions |
The kernel is versioned rather than chaptered: the repository keeps src/ at the final state and
evolution_by_versions/ with the intermediate ones, so a reader who falls behind can rejoin at a
chapter boundary. That is a cumulative single artifact, which is what puts it under
build-from-scratch rather than beside the notebook-per-technique
executable curricula.
What it assumes, and what it refuses to assume
Prerequisites are stated exactly and they are small: basic C — "defining variable and functions, pointers and so on, you don't need to be a master on C's libraries." Assembly is explicitly not assumed. "Every aspect you need to learn about x86 assembly in order to create 539kernel will be explained in this book," and chapter 1 duly opens with what a register is.
That is the opposite decision from the rest of this corpus. coding-interview-university and awesome-system-design-resources hand a reader a list of other people's material; adrianhajdin-uber-clone integrates five vendor SDKs and implements none of them. Here the toolchain is named down to the version — GCC 7.5, NASM, GNU Make, QEMU or Bochs — and everything above the hardware is written by the reader. The dependency count is zero, which is also why the book has aged better than a link farm would have: nothing in it can rot except the compiler version.
The ending is the interesting part
Chapter 7 does not point at a job. After the kernel boots, the book turns to research papers and walks through five: in-process isolation and the Endokernel (with a section titled "Lord of x86 Rings"), the nested kernel, the multikernel, dynamic reconfiguration via THINK's Fractal component model, and unikernels — closing on HermiTux, a binary-compatible unikernel that can run an unmodified Linux application.
The author gives the two exits names. A traditionalist implements the well-known concepts of traditional operating systems; a kernelist "searches for other better solutions for the given problem and designs an operating system kernel that uses these solutions," and the stated way to find those solutions is to read papers, because "most probably, these ideas haven't been implemented or adopted by others yet." The chapter's declared goal is "to encourage interested people to start looking to the scientific papers and implement their solutions."
No other curriculum in this corpus ends in the literature. coding-interview-university and awesome-system-design-resources end at a hiring interview, developer-roadmap at a job title, kernel-exploit-dojo at a CTF scoreboard, adrianhajdin-uber-clone at a portfolio piece. This one ends by handing the reader a reading list of unimplemented research and telling them to go build one. It is the corpus's first curriculum whose exit is production of new work rather than assessment, and it is worth watching whether that is a property of systems programming or of this author.
Tier, and the one quality signal
T1, re-tiered 2026-08-21 under tier by the claim, not the URL. What this page rests on is the book's own contents — 215 pages, seven chapters, the stated prerequisites, the version-per-chapter scheme — read directly from the PDF. A book is the primary source for what is in it, and every one of those facts is checkable against the artifact.
The caveat is unchanged and it does not live in the tier. One author, no publisher, no outcome data, nothing measuring whether a reader finishes or learns. That is the corpus's standing hole in meta-curriculum, and it would still be true if this book were peer-reviewed. It was being carried by the T3 grade, where it distorted a number meant to rank source quality across 36 spokes; it is carried here instead. Any claim this book makes about how well it teaches is still the maker's, and still T3 if leaned on.
Two things distinguish it even so. It was read before release by an academic, Dr. Hussain Almohri, whom the acknowledgements thank for feedback and discussion — the only pre-publication review any source in this spoke records. And it is the corpus's second publisher with nothing to sell, after mito753: no course, no book upsell, no newsletter, no sponsorship, no Academy. The free PDF, the free website and the GitHub repository are the whole offer. The "individual self-publisher with a commercial layer" pattern the spoke tracked at 3/3 is now 3/5.
What is missing
No exercises, no problems, no assessment of any kind — the reader's only check is whether the kernel boots, which is a real signal but a coarse one. No stated audience beyond "knows some C," no time estimate, and no errata or revision history since November 2022. The repository is the only place a reader could report a defect, and nothing here records whether anyone has.
Adjacency worth logging: no spoke in this hub owns operating systems. This book files here as a teaching artifact, per the spoke's boundary rule, and its subject matter has no home. If two more systems-programming sources arrive, that is a spin-out to consider rather than a pile to keep filing under pedagogy.
Related
build-from-scratch · mohammed-q-hussain · executable-curriculum · clone-project · meta-curriculum · kernel-exploit-dojo · coding-interview-university · ai-engineering-from-scratch · synthesis