Then, without installing another distro over the top of it, slowly convert it into another distro by replacing package managers, installed packages, and configurations.
System must be usable and fully native to the new distro (all old packages replaced with new ones).
No flatpaks, avoid snaps where physically possible, native packages only.
EDIT: Some clarification on some of the clever tools brought up here:
chroot, dd, debootstrap, and partition editors that allow you to install the new system in an empty container or blanket-overwrite the old system go against the spirit of this challenge.
These are very useful and valid tools under a normal context and I strongly recommend learning them.
You can use them if you prefer, but The ship of Theseus was replaced one board at a time. We are trying to avoid dropping a new ship in the harbor and tugging the old one out.
It may however be a good idea to use them to test out the target system in a safe environment as you perform the migration back in the real root, so you have a reference to go by.
Easy: pick two similar distros, such as Ubuntu and Debian or Manjaro and Arch and go from the base to the derivative.
Medium: Same as easy but go from the derivative to the base.
Hard: Pick two disparate distros like Debian and Artix and go from one to the other.
Nightmare: Make a self-compiled distro your target.
I've done the Arch to Artix. It wasn't hard, per se, but it took a while. I think that should be Medium, because Artix isn't just an Arch derivative.
In fact, might I suggest a different way of looking at the difficulties?
Replacing the package manager: Hard.
Replacing the package manager without a live USB: Extreme.
Going from a basic systemd-based distro (init, log, cron) to anything else: Hard
Going from a systemd distro that's bought into the entire systemd stack, including home and boot: Extreme
Going from one init to another: Medium
Changing boot systems: grub to UEFI, for example: Easy.
Replacing all GNU tools with other things: Extreme (mainly because of script expectations).
And so on. You get 1 point for Easy, 2 for Medium, 4 for Hard, and 8 for Extreme. Add 'em up, go for a high score.
I don't think rolling your own is that hard, TBH, unless you're expected to also build a package manager. If maintaining it would be harder than building it.
Then kexec to alpine's kernel and the initramfs generated by its installation (which would incidentally "replace" PID 1 with the new /sbin/init). For clean up you could take a diff of "tar -t" for all the installed packages from both distros then delete the files only in the old distro's packages.
Make a self-compiled distro your target.
Replace the first step with a compilation of apk, abuild everything required by alpine-base and linux-lts (git clone aports to bootstrap that work), then add the package directory to /etc/apk/repositories before the second step. Next, begin to worry that you haven't fully broken free yet, replace abuild with a bespoke mybuild and apk with tar -x, grapple with signed binaries, reflect on your own identity and authenticity, then take a tour through gentoo and find yourself missing the $HOME you left and its familiar comforts.
After completing the challenge and making sure your system is usable and can survive a reboot:
If you've kept the old package manager, search for installed packages and make sure that the package manager itself is the only thing left. Then delete it.
Reminds me of MattKC, a guy on YouTube who does similar stuff. He ported the .Net framework to win95. very interesting videos, if think this challenge would be exactly his type.
The beauty of this exercise is you can make it as easy or challenging as you want just by changing the targets, and finding different combinations can keep things interesting.
I "broke" linux mint just by trying to pop KDE on, had to timeshift because it messed up my keyboard layout and a whole bunch of other things with my display.
I don't know how people do these crazy changes without pain, and have a feeling the answer is simply "there's pain" 😂
Reminds me of trying NsCDE… it changed a ton of settings and no other desktop looked right after that. I ended just blowing away my home folder and restoring my files
I can't find it now but basically something like that yeah. VPS provider only gave them SSH on linux so couldn't run the openbsd installer any normal way either
“Medium: Same as easy but go from the derivative to the base.”
I can't quite recall, but I think I did exactly that with Ubuntu -> Debian once upon a time. I think Ubuntu was only a year or so old though, so there wasn't a huge amount of divergence back then. As a bonus anecdote I also attempted a semi-successful build of Gentoo on a PPC Mac around the same time (nothing before or after that has compared in its level of nightmare).
I also attempted a semi-successful build of Gentoo on a PPC Mac around the same time (nothing before or after that has compared in its level of nightmare).
I have seen dozens of systems migrated from Gentoo to CentOS by live swapping the userspace and eventually rebooting into the new kernel. A hair raising experience to be sure.
I once switched from Debian i386 to amd64 in-place. That was MUCH harder than you would expect, I guess somewhere between medium and hard in your list. That server is still running that install btw, so in the end it all worked out.
i did a bit of back and forth with a couple of debian based distros in the past but it always ended up buggy and weird. it was a desktop install though, i imagine servers would be simpler.
I had forgotten about doing that myself. I did that on a couple servers once the distros had full 64 bit builds. Does that technically count as an architecture swap in-place as well?
I think it would be very interesting to convert e.g. a regular Fedora installation into a (so-called “immutable”) Fedora Silverblue installation or vice-versa.
This goes against the spirit of the challenge, but as its a singleplayer game (unless you bring friends and SSH!) you can definitely choose to allow dd, chroot, and similar tools
it is pretty terrifying to debootstrap over ssh. constantly checking that you're on the correct system, and using the chrooted terminal. it's like a high wire act. at least the first few times.
Is that even possible? I'm already in panic when I remove a package and it's dependencies with pacman 😅.
Sure I did replaced Thunar with Nemo, but a few things don't work exactly how it should, like opening the download directory from Firefox (Known issue BTW) even though all mime-types are correctly set !
Even switching from Alternative -> Base distro seems like a really difficult task :/
I am not educated enough about this, but don't these kind of games unnecesarrily strain all the servers that host the packages for people that really need them for download and most of these people run these servers for free in good will and faith that they will serve meaningful needs with positive impact? I am sorry for spoiling the fun, but I felt like I had to point this out.
As other commenters have said, its about as strenuous as doing two normal installs.
However, if you want to do this challenge but feel guilty about the consumed resources, consider donating to the two distros you are performing this with to cover any additional service costs. In all likelihood it'll only cost them fractions of pennies, but any reason to donate to FOSS is always appreciated.
How is this any less meaningful than any other use case? Is downloading a distro to play video games ok? To shitpost on social media? To watch clickbait videos on youtube? Why is this in particular a bad use of resources?