I have an old notebook which I’ve been toying with a few smaller distros on (typically easy to install, liveCD types), and while I enjoy the tinkering aspects of this, I had a thought that I’ve been mulling.
In the past I’ve run distributions based on larger, better supported, systems (Ubuntu, Debian, Arch, etc.) and if or when they have folded, like crunchbang did, or PeppermintOS (however briefly), I just changed them out.
However, if I were to go back to peppermintOS, say, would it be feasible to ‘convert’ the system to the parent distribution? So, could I force peppermintOS to ‘become’ Debian, for example? Or is this overly simplistic? It’s a level of engagement with my operating systems that I just haven’t had!
The problem with package based distros (everything non-immutable) is, that a distro is very complex.
Even if you manage to “swap out” the package repositories, you usually still have a lot of remaining stuff in the background and many things tweaked by the maintainers. It’s a huge mess.
In theory, you could absolutely do that, but to be honest, why bother? You already always should have a backup of all your personal data, so why not reinstall it cleanly?
Speaking of image based distros (“immutable”), the cool thing about most is that that you can easily swap out the underlying OS with just one command.
For example, you can always rebase from Fedora Silverblue to Kinoite to Bazzite to something with Hyprland and then back to vanilla Silverblue, without any traces.
So, for example, if the guy who makes your custom image on Github stops maintaining it, you can simply switch to something else in just seconds.
Maybe this is something relevant for you :)
Tiny vocab tip: “Non-immutable” is actually just called “mutable”.