when you upgrade an OS, do you clean install or upgrade?
clean install: you make a backup, nuke the computer, install a fresh upgraded copy of the distro you want from a live usb, copy your data again to the computer.
upgrade: you wait ‘till the distro’ developers release an upgrade you can directly install from your soon to be old distro, you use a command like sudo do-release-upgrade
Wait for the distro to officially release an upgrade path. Only do a fresh install if it doesn’t work.
On Windows however whenever I would get a new pc in which I was prepping for staff(I worked in IT) the first thing I’d do after unboxing it is a wipe of the factory Windows install and do a clean install with the latest ISO from Microsoft.
No bloatware, network managers, anti virus etc nonsense. We had all of our own stuff for that which applied via Group Policy anyway.
I’ve got a desktop that got a dirty install of KDE Neon when the repositories first got put up (before there were isos). Been in-place upgrading it ever since.
Man just when I thought I got the hang of NixOS and setup everything already thanks to the new wiki. I dont think this is worth the trouble for me right now, but maybe in the future.
On my personal laptop with openSUSE, I have plenty confidence doing all kinds of upgrades and sidegrades (between Leap and Tumbleweed).
The package manager detects conflicts and makes me decide what to do with them. I’ve never seen the software or distro dependency definitions fuck up, it was always me making a wrong decision.
Well, and if I do make a wrong decision or anything else should go wrong during the upgrade, I can roll back to the BTRFS snapshot before.
On my work laptop, the best I can get is Kubuntu. Apt is much more fickle, since it doesn’t have as clear of a concept of what constitutes a conflict, but also what a correct system should look like.
The whole packages feel much more fickle, too, because they’ve got all these custom patches, so you really don’t want to accidentally mix different versions of packages, like might happen in an incomplete upgrade.
And of course, you get one chance at upgrading. If anything goes sideways, you better have your Live USB ready right away.
So, that’s why I would prefer to install fresh right away. Of course, my workplace doesn’t actually allow me to do that either. They really like to keep me on edge.
It depends on how many versions I am away from the latest, and how much I've messed with the distro.
Usually I stay on an Ubuntu LTS and upgrade from LTS to LTS when that upgrade path is ready. I upgraded from 20.04 to 22.04 this way.
But this time I wanted Pipewire in 24.04, and didn't want to wait for a 22.04 to 24.04 upgrade to be ready. I'm using a bluetooth headset and Pulseaudio is pretty terrible at switching headset profiles. Between not wanting to upgrade an upgraded install, and having messed with Pulseaudio quite a bit trying to get it working, I went ahead and clean installed 24.04 and moved some configs over.
I follow the official upgrade method. Can’t be bothered to mess around with anything more complicated than that. Besides, the devs probably understand the system better than I do, so there has to be a reason why that is the preferred way.
This is my plan A. I’ll only go to plan B if something goes wrong — which has happened to me a couple times. I tried to upgrade Ubuntu (LTS, I forget which version) years ago, but it failed hard. I still don’t know why. It wasn’t something I could figure out in half an hour, and it wasn’t worth investing more time than that.
Come to think of it, it’s possible all my upgrade woes came down to Nvidia drivers. It was a common problem on Suse (TW), to the point where I pinned my kernel version to avoid the frequent headaches. I’ll try a rolling distro again when I switch to AMD, maybe.
I feel like that may be true nowadays, but I remember back when I used to use ubuntu that the upgrade from 16.04 to 18.04 was pretty bad. Fedora has always worked great for me, but these days I only use rolling release distros in which case there aren’t any major version updates in the first place, so the problem largely doesn’t exist in the same context.
Canonical makes ubuntu makes upgrades break on purpose so they can sell you ubuntu pro that has the fix in it. For example the upgrade you mention broke grub but only the paid support release ring/branch has a fix
I upgrade when it’s a distro that releases new versions regularly (for example Fedora with two releases per year). I obviously also upgrade rolling distributions.
Why? Because it’s less work and I haven’t had many problems with it.
I usually clean install long-term distros like RHEL (or RHEL-based). These don’t always have a good upgrade path and I usually only use them on servers.
upgrades have been working fine here, both linux and windows, for well over a decade.
only if a system is also being repurposed at the time of the 'upgrade', or if i'm changing the connection type of the boot drive (such as from sata to nvme, or switching an older system to ahci mode) do i install 'from scratch'.
Add comment