News

DF-Linux with Its Own Linux Kernel

Scope: This report documents the kernel-specific work reported and checked so far. It distinguishes the present unmodified reference kernel from the planned DF-Linux kernel variant. No independent access to the build artifacts was used.

DF-Linux with Its Own Linux Kernel
John-Ruhne Nilsen

John-Ruhne Nilsen

Published: 17.11.2026 12:09

Oppdatert: 17.11.2026 12:15

1. Executive status

The Linux 6.18.63 reference kernel was obtained from upstream source, its archive signature was reported as verified, configured using x86_64_defconfig, compiled, and boot-tested in QEMU/KVM. Kernel initialization was observed. Boot stopped when the kernel could not mount a root filesystem, as no root filesystem or user-space environment had yet been provided.

Current status: reference kernel successfully compiled and preliminarily boot-tested; a complete DF-Linux system has not yet booted.

2. DF-Linux will have its own Linux kernel

DF-Linux is intended to ship its own configured, tested and maintained variant of the Linux kernel, derived from the upstream Linux source code. This is not a plan to write a new kernel from scratch. The first compiled Linux 6.18.63 image is an unmodified reference build, not yet a DF-Linux-specific hardened kernel.

Subsequent development will evaluate security requirements, select and document kernel configuration changes, and consider source-code modifications only where justified. Each proposed change will be compared against the unchanged reference build through reproducible functionality, security and performance tests. An eventual DF-Linux-specific release identifier may be adopted, but none has been assigned or produced so far.

3. Completed kernel work

  • Obtained linux-6.18.63.tar.xz and its detached signature from kernel.org.
  • Checked the source archive signature using GnuPG and identified the signing key fingerprint (reported complete; exact output not reproduced here).
  • Extracted upstream sources to 01-kildekode/linux-6.18.63/.
  • Generated the reference kernel configuration with x86_64_defconfig and preserved it as 02-kjernekonfigurasjon/linux-6.18.63-referanse.config.
  • Compiled the x86-64 bzImage in a separate output directory with six concurrent make jobs.
  • Confirmed the resulting bzImage as a Linux 6.18.63 x86 boot executable, build #1, with SMP and PREEMPT_DYNAMIC.
  • Launched the resulting reference kernel in an isolated QEMU/KVM test and observed early initialization.

4. Recorded reference build

Source tree: /media/johnruhne/DF-Linux/01-kildekode/linux-6.18.63

Build output tree: /media/johnruhne/DF-Linux/03-bygg/linux-6.18.63-referanse

make -C /media/johnruhne/DF-Linux/01-kildekode/linux-6.18.63 \
O=/media/johnruhne/DF-Linux/03-bygg/linux-6.18.63-referanse \
-j6 bzImage

BUILD arch/x86/boot/bzImage
Kernel: arch/x86/boot/bzImage is ready (#1)

Kernel image: /media/johnruhne/DF-Linux/03-bygg/linux-6.18.63-referanse/arch/x86/boot/bzImage

5. First QEMU/KVM boot test

timeout 30s qemu-system-x86_64 \
-enable-kvm -m 2048 -smp 2 \
-kernel /media/johnruhne/DF-Linux/03-bygg/linux-6.18.63-referanse/arch/x86/boot/bzImage \
-append "console=ttyS0" -nographic -no-reboot

  • Linux 6.18.63 initialized within the KVM virtual machine.
  • Two guest CPUs and 2 GiB of guest memory were detected.
  • Boot messages indicated NX protection and Kernel/User Page Table Isolation.
  • SELinux initialization was seen; enforcement of an active policy was not demonstrated.

VFS: Cannot open root device "" or unknown-block(0,0)
Kernel panic - not syncing: VFS: Unable to mount root fs

Interpretation: The kernel reached the root-filesystem mounting stage, but no root filesystem was supplied. This is consistent with the limited kernel-only test; it does not establish a successful user-space boot.

6. Preparation for the first user-space boot

BusyBox was found at /usr/bin/busybox. The command “ldd /usr/bin/busybox” returned “not a dynamic executable”, consistent with static linking. This makes the available BusyBox a suitable candidate for a minimal initial user space without shared-library dependencies.

The existing 04-testing directory was listed and contained clevo-control-center/, tuxedo-drivers.tar.gz and tuxedo-inspeksjon/. These contents must be preserved. Creation of 04-testing/rootfs-referanse/ was proposed but has not been confirmed by a terminal result.

7. Limits of current evidence

  • No initramfs or usable DF-Linux root filesystem has been booted.
  • No PID 1, BusyBox shell or other first guest user-space process has been verified.
  • No DF-Linux-specific kernel patch or hardened kernel configuration has yet been demonstrated.
  • No demonstrated SELinux enforcing policy, login, desktop, package manager or distribution installation.
  • No controlled benchmark currently establishes DF-Linux as more secure or faster than the upstream reference.

8. Next development milestone

Create and test a minimal reference root filesystem and initramfs, using the statically linked BusyBox where suitable. Boot the unchanged Linux 6.18.63 image in QEMU/KVM and verify execution of the first user-space process. Preserve upstream sources, the unmodified reference configuration and existing testing files. Continue with one terminal command and one observed result at a time.

9. Evidence basis

The DF-Linux project handover of 17 November 2026, together with reported terminal build/boot outputs and subsequent BusyBox and directory-listing outputs, forms the basis of this report. Project Assignment, Version 0.1 (16 November 2026), provides the planned development approach. Michael Kofler, Linux: The Comprehensive Guide (2024), is a technical reference. The project assignment predates the completed build and first boot test.