📘 Linux Kernel Programming – Chapter 2
Building the Linux Kernel from Source
Part 1 — What we are building, how Linux versions work, and how the kernel development community actually operates.
🎯 What You Will Learn in This Part
- Why building the kernel from source is a valuable skill
- The three components every Linux system must have
- How to read and interpret a Linux kernel version number
- How the Linux kernel development process actually works
- The different types of kernel source trees you will encounter
1. Why Would You Build the Kernel from Source?
When you install Ubuntu or any Linux distro, it comes with a pre-built kernel. That is convenient — but it also means you are running what someone else decided is a good enough for everyone kernel. In embedded systems and kernel development, that is rarely acceptable.
Building the kernel yourself gives you complete control — you decide which features are compiled in, which drivers are included, what is optimised for your hardware, and what is left out entirely. This is not just a learning exercise; it is the real workflow that embedded engineers and kernel contributors follow every day.
💡 Think of it this way:
A pre-built distro kernel is like a readymade pizza — convenient but someone else chose the toppings. Building from source is like cooking your own — you pick every ingredient for your specific taste and hardware.
This chapter (split across three parts) walks you through the complete process step by step: downloading the source, understanding the layout, configuring what you want, and finally compiling and installing. For now, we lay the foundation.
2. Three Things Every Linux System Must Have
Before we dive into building the kernel, let us take a step back and understand what actually makes a Linux system boot and run. Whether it is a massive data-center server, your laptop, or a tiny IoT sensor — every Linux system has exactly three mandatory components:
In this chapter our entire focus is the middle piece — the kernel. We will not dig into root filesystem internals here. For the bootloader, we will only touch GRUB configuration briefly and only on x86 machines, since that is the most common development setup.
📌 Good to Know:
On embedded systems the bootloader is often U-Boot instead of GRUB, and the root filesystem might be a minimal BusyBox image or a Buildroot-generated filesystem. The concept is the same — three layers, always.
3. Understanding Linux Kernel Version Numbers
Every Linux kernel release has a version number. You have probably seen strings like 6.8.0-45-generic or 6.6.30 and wondered what each part means. Let us break it down properly.
On any Linux machine, run this command to see your current kernel version:
$ uname -r
6.8.0-45-genericThe format follows this pattern:
major.minor[.patchlevel][-EXTRAVERSION]
Also written as: w.x[.y][-z]| Part | Symbol | Example | What It Means |
|---|---|---|---|
| Major | w | 6 | The main kernel series. Changes very rarely — only when there is a truly significant architectural shift. |
| Minor | x | 8 | Increments with every regular release cycle (roughly every 2–3 months). This is the number you will see change most often. |
| Patchlevel | y | 0 | Optional. Applied to stable kernels for critical bug or security fixes between regular releases. A kernel like 6.8.3 has patchlevel 3. |
| EXTRAVERSION | -z | -45-generic | Optional. Also called localversion. Used by distributions to track their own internal changes, patch sets, or flavours. |
Decoding a Real Version Number
Let us decode 6.8.0-45-generic piece by piece:
⚠️ Important Note:
Distribution kernels (Ubuntu, Fedora, RHEL) may not follow this convention strictly — they add their own version suffixes and backported patches. Only vanilla kernels from kernel.org are guaranteed to follow this format cleanly. When we build our own kernel later, we use the vanilla source.
📖 Historical Trivia:
In kernels older than 2.6, an even minor number meant a stable release and an odd minor number meant a development build. That convention no longer exists — do not let old documentation confuse you on this point.
Where Does the Vanilla Kernel Come From?
The official Linux kernel source is published at kernel.org. The Linux Foundation — a non-profit organisation — stewards the kernel project and keeps the repository publicly available at no cost. This is where we will download our source code in Part 2.
✅ Key Terms to Remember:
- Vanilla kernel — the pure, unmodified kernel source from kernel.org. No distro patches.
- Distribution kernel — a vendor-modified kernel with custom patches and security backports (e.g., Ubuntu’s kernel).
- Stable kernel — a vanilla kernel branch receiving only critical fixes, suitable for production use.
4. How the Linux Kernel Development Process Works
Many people assume the Linux kernel is developed chaotically — thousands of random contributors pushing code without any structure. That is far from the truth. The Linux kernel has one of the most disciplined and well-documented development processes in all of open-source software.
Here is a simplified view of how the release cycle flows:
~2 weeks
rc1 → rc7 (~6–8 weeks)
e.g., v6.9
Types of Kernel Source Trees
When you explore kernel.org you will encounter different types of kernel trees. Knowing which one to use matters:
🎯 For This Series:
We will download and build a stable vanilla kernel from kernel.org. This gives us a clean, known-good codebase without any distro-specific noise — perfect for learning the build process and kernel internals.
5. The Build Steps — A Quick Preview
Now that you understand the context, here is a bird’s-eye view of the complete kernel build process we will follow across all three parts of this chapter:
| Step | What Happens | Covered In |
|---|---|---|
| 1. Obtain Source | Download the kernel tarball from kernel.org | Part 2 |
| 2. Extract | Unpack the tarball and explore the source tree layout | Part 2 |
| 3. Configure | Run menuconfig and select what to build in or out | Part 2 |
| 4. Compile | Run make to build the kernel image and modules | Part 3 |
| 5. Install | Install modules and kernel image, update GRUB, reboot | Part 3 |
🔑 Quick Summary — What We Covered
- Building the kernel from source gives you full control over what runs on your system
- Every Linux system needs exactly three components: bootloader, kernel, root filesystem
- The kernel version format is
major.minor[.patchlevel][-EXTRAVERSION] - The minor number increments with each release; EXTRAVERSION is distro-specific
- The kernel has a well-defined release cycle: merge window → RC phase → stable release
- For learning, always use the vanilla stable kernel from kernel.org