


ExaNeSt_H2020
7K posts

@ExaNeSt_H2020
H2020 project, developing solutions for Interconnection Networks, Storage, and Cooling for exascale-level supercomputers, tuning real HPC Applications.









Join the webinar on Open Source and European Sovereignty for HPC to explore the realities and challenges 📅 22 May 2026 🕚 11:00–12:00 CEST Speakers • Thierry Goubier • Gaël Blondelle Sign up!👉 register.gotowebinar.com/register/22203… #HPC #OpenSource #DigitalSovereignty #EuroHPC










You've installed Linux a dozen times. The installer asked you the same questions every time. Disk layout. Username. Timezone. Keyboard. A progress bar. A reboot. The installer is a wizard around a process that isn't really wizardry. Underneath, it's copying files into directories, writing a few config files, installing a bootloader. That's it. That's the whole job. The reason this matters: as long as the installer is the only way you know how to produce a Linux system, you're stuck with the kinds of systems installers are designed to produce. General-purpose desktops. General-purpose servers. The shapes someone else decided were worth shipping. Skip the installer and the shape is yours. The catch is that "skip the installer" sounds like the kind of thing only kernel developers do and it isn't. Alpine Linux has a tool called apk.static, a single statically-linked binary that runs on any Linux. You point it at a target directory, hand it a list of packages, and it populates that directory with a working Alpine root filesystem. Tar the directory, hand the tarball to QEMU as an initramfs, and you have a Linux system you built on purpose, booting in a VM, in a few commands. Once you've done that, the installer stops being the thing that produces Linux systems. It becomes one possible front-end, among many, for a process you now control directly. And once you control the process, you can shape the output. The list of packages is yours. The init script is yours. A bootable Linux image stops being something you receive and starts being something you assemble, with a clear input and a predictable output. The new series walks through it from the first command. Starts soon on The Linux Field Guide: lfg.popovicu.com









