Here's an exercise in extreme masochism:
-
Reminds me of a recent post someone converted their system from Debian to OpenBSD via SSH only
Why does that sound familiar.
Did they load an OS into ram to run ssh then rebuild the machine, also some VPS that the provider was dragging their feet on remote hands.
-
Why does that sound familiar.
Did they load an OS into ram to run ssh then rebuild the machine, also some VPS that the provider was dragging their feet on remote hands.
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
-
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"
wrote on last edited by [email protected].
-
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.
wrote on last edited by [email protected].
-
The Linux Ship of Theseus
-
pick any distro and install it.
-
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.
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.
-
-
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
-
The Linux Ship of Theseus
-
pick any distro and install it.
-
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.
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 got a blank macbook air at home waiting for a project.
I've never undergone a project like this without cheating by using bedrock linux as an intermediary then "Unbedrocking" my install (officially impossible, unofficially insane) with another PM as my default to convert from debian to arch years ago.
This is gonna be fun, or hellish, idk I'll find out.
-
-
The Linux Ship of Theseus
-
pick any distro and install it.
-
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.
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.
Easymode: pick a fedora ublue distro and go from bazzite to silver blue
::: spoiler Title
You can rebase with a single command I think.
::: -
-
So, any distro to any other distro?
- Installs Fedora Silverblue
- Rebases to Bazzite
Jobs done chief!
Bazzite on GNOME? Rebasing from GNOME to KDE causes so many headaches. Ask me how I know (yes I'm aware they tell you not too).
-
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.
I like it
-
I would watch a YouTube series doing this
Not quite the same but you might like the Linux from Nothing series, building out a Linux install from first principles.
Obviously lots of linux youtubers have done videos on linux from scratch too but the step by step nature is pretty enjoyable to watch.
-
System shared this topic on
