Linux

· Lars Nielsen

A Build Step That Needs the Internet, Inside a Chroot That Doesn't Have It

A build running inside a chroot on this project has no network access, by design — every source tarball is fetched ahead of time and extracted locally, and nothing in the build process is supposed to reach outside the machine while a package compiles. One package's default configuration quietly assumes otherwise.

Read article A Build Step That Needs the Internet, Inside a Chroot That Doesn't Have It
· Lars Nielsen

One Data File Added Because a Build Script's Fallback Path Doesn't Exist

One package in this from-scratch build's KDE stack contains no compiled code at all. It's a database of hardware IDs — PCI, USB, and PNP vendor and device names — and it exists only because a different package's build script checks for a specific file at configure time, before anything about hardware detection actually matters at runtime.

Read article One Data File Added Because a Build Script's Fallback Path Doesn't Exist
· Lars Nielsen

A Vulkan Helper That Can't Exist Because Qt6 Was Never Built With It

Most of the compatibility work in this build's KDE packages involves code that compiles fine but never actually runs — dead paths behind a runtime check that always evaluates false. This one is different: two small helper programs that don't compile at all, because the graphics toolkit underneath them was never built with the one feature they need.

Read article A Vulkan Helper That Can't Exist Because Qt6 Was Never Built With It
· Lars Nielsen

Wiring GRUB Into a System That Already Triple-Boots, Without Touching the Other Two

This machine already runs two operating systems off one disk, sharing one EFI System Partition. Adding a third meant writing to that same shared partition and to the machine's live EFI boot configuration — real, hard-to-reverse changes on hardware two other working systems depend on, not a fresh disk with nothing to lose.

Read article Wiring GRUB Into a System That Already Triple-Boots, Without Touching the Other Two
· Lars Nielsen

The Shortcut That Almost Fixed Twenty Files at Once, and Why It Couldn't

Twenty files in one KDE package needed the same fix: remove an unconditional include of a header that doesn't exist on this system. Patching all twenty by hand looked avoidable. One upstream flag, flipped the other way, looked like it would satisfy the missing header everywhere at once. It didn't — and the reason it couldn't is more specific than "it didn't work."

Read article The Shortcut That Almost Fixed Twenty Files at Once, and Why It Couldn't
· Lars Nielsen

A Kernel Config Copied From a Working Install Almost Broke the Boot Anyway

A previous attempt at building this system from scratch failed at wifi — a real driver problem that killed that attempt outright. This time, the kernel config started from the one place guaranteed to already have that driver working: this exact machine's own currently-running Ubuntu kernel. That choice fixed the wifi problem completely.

Read article A Kernel Config Copied From a Working Install Almost Broke the Boot Anyway
Subscribe to Linux