There's a spectrum of "build your own Linux." On one end, you run an installer. On the other, you run Buildroot or Yocto: compile the kernel, the toolchain, every userspace package from source. The build can take hours. The output is a turnkey image that's yours top to bottom.
Most people only ever see the installer end, which is what makes the installer feel like the whole map.
The Linux Field Guide is going to walk you, eventually, all the way to the deep end. Building a distro from scratch, kernel and userspace and all. We're not there yet. The guide is for upper beginners and we're going to earn that ground in pieces.
This is the first piece. A quick dopamine hit, sitting closer to the installer end than to Buildroot, but with the inputs in your hands.
We don't compile the userspace. We stitch together prebuilt Alpine packages with a script that finishes in seconds and is short enough to read in one sitting. Declare a list of packages, a target architecture, the repositories to pull from. The script runs apk.static against a directory we own. The output is a tar of a root filesystem of our exact specification, ready to boot in QEMU.
So why bother, if it's not the from-source build?
Because the script is the spec. Run it today, run it next month, run it on a coworker's machine, and the output is the same artifact. The system stops being a thing you set up once and forget how. It becomes a recipe you can read, edit, and re-run.
Because it's the right shape for what comes later. Once you've internalized that the system is a directory of files produced by a script, swapping apk.static for a Buildroot pipeline is a different script with the same shape. The installer mental model doesn't generalize. This one does.
That's the slice this series teaches. Coming soon on The Linux Field Guide:
lfg.popovicu.com