Driving Linux From Scratch With make: Version-Named Stamp Files and Resets That Keep the Downloads
The Linux From Scratch book is a list of commands to type, in order, over a few hundred pages. Typing them once is the point of the exercise.
The Linux From Scratch book is a list of commands to type, in order, over a few hundred pages. Typing them once is the point of the exercise.
One morning in August, a worker container in my search engine had been using about 86% of a CPU core for nine hours and producing no output at all. docker top showed only one busy process: the shell script that runs the worker, not the PHP program it starts. The script was stuck in a loop around wait.
Between August and September I built a Linux From Scratch system on my ThinkPad, scripted end to end, and took it from an empty partition to a KDE Plasma desktop that I now do my work on. Along the way I wrote up the problems one at a time, as separate articles. This is the map: the build in the order it happened, a sentence or two on each problem, and a link to the full story.
The script that publishes articles on this site tests every article on a local copy of the site first, at https://linkhub.ddev.site. That local site runs in DDEV, and its HTTPS certificate is signed by a local certificate authority that mkcert created. On the Ubuntu install where the pipeline started, that just worked.
This build's wifi documentation got rewritten once the desktop environment grew a GUI network applet — not because the original instructions were wrong, but because a second, complete way to do the same thing now existed alongside the first, and the two actively fight each other if both run at once.
Linux From Scratch builds coreutils with an extra patch, the i18n patch, which adds multibyte character support to tools like cut and expand. In my scripted LFS build, applying that one patch took four rounds of fixes spread over eleven days.
After I fixed the wrapper script for this site's article pipeline so it no longer carries on without its grammar checker, I added one more line to its cleanup function: wait for the LanguageTool server to exit after killing it, so its port is free by the time the script returns.
On the database server of my search engine project, /etc/ssh/sshd_config said PasswordAuthentication no. The server accepted password logins anyway, and a bot on the internet was guessing the root password around the clock. Every attempt failed, but only because the password held, not because the setting did.
I went looking for this laptop's crontab to write a comparison with systemd timers, and there wasn't one. No crontab binary, no /etc/cron.d, no cron daemon running at all — crontab -l just says command not found.
My from-scratch Linux build boots into a KDE Plasma desktop now, and for a while it booted into one with a strange set of problems. Wi-Fi scans in NetworkManager didn't work. Power management didn't work. Login sessions weren't being registered properly. Three subsystems with nothing obvious in common, all broken at once.