Anonymous
8/6/2025, 4:16:05 PM No.106162592
I've looked into the bootstrapping process of Gentoo since after eight years of using it as my daily driver I was interested, and the Catalyst/stage3 creation process looked like it would be possible to automate. Here is the idea:
>Create a simple script that could add packages and their dependencies automatically to the stage3 spec files.
>Compile everything on the host system to effectively create a stage4 archive.
>Turn the stage4 into a mountable archive.
>Use GRUB to pick from a list of stage4 archives to boot from from an archive store, automatically adding the latest build to the main menu option.
>Cache everything used during the build to avoid having to rebuild the entire image to add a single new package. Keep the portage cache in a mutable subvolume that can be used across rootfs images.
>Allow overlays to let the user modify an existing rootfs in case they need something immediately and cannot find the time to create a new image.
>Have a dedicated "Config" subvolume that contains the base /etc and /home/$USER/.config directories before they are added to the final, usable system.
This doesn't sound too hard to automate. In fact, I know that because someone already did. Looking up if anyone has done this before lead me to some niche distribution called Xenia Linux which seems to have issues such as deprecating OpenRC due to relying on Flatpak instead of baking in packages to the rootfs. Still, this sounds like something that could be done over a few days with a few scripts. It would be the perfect distribution.
>Immutable and atomic but
>Still allows non-bloat installation of packages.
>Reproducibility as a side effect of the building process.
>Proper USE flags availability to not have to deal with Nix autism and Guix non-existence when it comes to source configuration.
>Trivially allows using a build server that serves the final images to all of your devices.
What would the catch be? Seems like the endgame of Linux to me.
>Tinkertranny!
Fuck off, nu-/g/.
>Create a simple script that could add packages and their dependencies automatically to the stage3 spec files.
>Compile everything on the host system to effectively create a stage4 archive.
>Turn the stage4 into a mountable archive.
>Use GRUB to pick from a list of stage4 archives to boot from from an archive store, automatically adding the latest build to the main menu option.
>Cache everything used during the build to avoid having to rebuild the entire image to add a single new package. Keep the portage cache in a mutable subvolume that can be used across rootfs images.
>Allow overlays to let the user modify an existing rootfs in case they need something immediately and cannot find the time to create a new image.
>Have a dedicated "Config" subvolume that contains the base /etc and /home/$USER/.config directories before they are added to the final, usable system.
This doesn't sound too hard to automate. In fact, I know that because someone already did. Looking up if anyone has done this before lead me to some niche distribution called Xenia Linux which seems to have issues such as deprecating OpenRC due to relying on Flatpak instead of baking in packages to the rootfs. Still, this sounds like something that could be done over a few days with a few scripts. It would be the perfect distribution.
>Immutable and atomic but
>Still allows non-bloat installation of packages.
>Reproducibility as a side effect of the building process.
>Proper USE flags availability to not have to deal with Nix autism and Guix non-existence when it comes to source configuration.
>Trivially allows using a build server that serves the final images to all of your devices.
What would the catch be? Seems like the endgame of Linux to me.
>Tinkertranny!
Fuck off, nu-/g/.
Replies: