MX Permanent Secure Upgrade Path? [Solved]
Re: MX Permanent Secure Upgrade Path?
I think the OP should accept that the devs are recommending fresh install, and have provided tools like:
1) User Installed Packages;
2) the installer being able to preserve /home while installing);
to help with fresh installs.
For now, I believe that the in-place migration/upgrade path provided is going to remain advice that comes with a caution/warning.
If you go that route, you may have to manually do your own troubleshooting. And all the more so if you have additional/third party repos enabled in your system.
For instance, Fedora - pretty big organisation - has official migration/upgrade path from one release to the next. I have used it every 0.5 years from Fedora 21 to Fedora 39. However, there are some years where I have had to try to sort out issues before the upgrade can go fully through. And this happens even though I disable the RPM Fusion [third party] repo before every migration.
Same with Kubuntu, Netrunner and KDE Neon, each of which I had tried to use the provided upgrade path over 3 consecutive releases. There are always some hiccups you have to solve yourself, maybe remove some packages, etc, before the upgrade can go through. And each of these 3 Ubuntu distros [which I used at different times of my life] always fully broke down after the 3rd migration. Bugs and lagginess just made these distros unpleasant to use after the 3rd migration.
1) User Installed Packages;
2) the installer being able to preserve /home while installing);
to help with fresh installs.
For now, I believe that the in-place migration/upgrade path provided is going to remain advice that comes with a caution/warning.
If you go that route, you may have to manually do your own troubleshooting. And all the more so if you have additional/third party repos enabled in your system.
For instance, Fedora - pretty big organisation - has official migration/upgrade path from one release to the next. I have used it every 0.5 years from Fedora 21 to Fedora 39. However, there are some years where I have had to try to sort out issues before the upgrade can go fully through. And this happens even though I disable the RPM Fusion [third party] repo before every migration.
Same with Kubuntu, Netrunner and KDE Neon, each of which I had tried to use the provided upgrade path over 3 consecutive releases. There are always some hiccups you have to solve yourself, maybe remove some packages, etc, before the upgrade can go through. And each of these 3 Ubuntu distros [which I used at different times of my life] always fully broke down after the 3rd migration. Bugs and lagginess just made these distros unpleasant to use after the 3rd migration.
Last edited by asqwerth on Tue Jul 23, 2024 12:50 pm, edited 1 time in total.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: MX Permanent Secure Upgrade Path?
The trick with that Chapter 4 is to know what parts are important for your system and what parts you can skip (as in: most of itanticapitalista wrote: Tue Jul 23, 2024 12:28 pm I'm sure the vast majority of new (Debian desktop) users haven't done so since that Chapter 4 Upgrades from Debian 11 (bullseye) is way beyond most users comprehension.

For MX I'm pretty happy with the state of things. If you're feeling adventurous you can always go for the inofficial in-place upgrade which works similar to Debian's regular upgrade procedure, but be prepared that it will probably take longer (i.e. troubleshooting something) than just reinstalling it anyway.
EDIT: Fedora's half-yearly upgrade cycle is the reason I dropped it on my systems for good. It works most of the time, but it's still too much of a hassle to do it twice a year in my opinion. I prefer either stable releases with 2+ years of support or full-rolling like Arch.
If it ain't broke, don't fix it.
Main: MX 23 | Second: Mint 22 | HTPC: Linux Lite 7 | VM Machine: Debian 12 | Testrig: Arch/FreeBSD 14 | Work: RHEL 8
Main: MX 23 | Second: Mint 22 | HTPC: Linux Lite 7 | VM Machine: Debian 12 | Testrig: Arch/FreeBSD 14 | Work: RHEL 8
Re: MX Permanent Secure Upgrade Path?
@anticapitalista, you have proved a very good developer with the antiX and in MX contribution, the point of my question is how MX can be more competitive with other Linux OS, since it is very innovative, but it lacks a very important element. If this is possible to happen, an easy permanent and secure upgrade, why not? Maybe I am completely mistaken, and my question is wrong since I am not a developer.anticapitalista wrote: Tue Jul 23, 2024 12:28 pm Have you ever tried to do a Debian full upgrade from one release to another?
I'm sure the vast majority of new (Debian desktop) users haven't done so since that Chapter 4 Upgrades from Debian 11 (bullseye) is way beyond most users comprehension.
If your case is solved, and you want to help other users, click on the Solved-Button on the top right of a user's post.
Don't forget a system backup!
Don't forget a system backup!
- Eadwine Rose
- Administrator
- Posts: 14698
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX Permanent Secure Upgrade Path?
Why should we be more competitive? That is not the goal of MX. It's not a race after all :)
MX-23.6_x64 July 31 2023 * 6.1.0-37amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX Permanent Secure Upgrade Path?
It's definitely troublesomeMadMax wrote: Tue Jul 23, 2024 12:49 pm ....
EDIT: Fedora's half-yearly upgrade cycle is the reason I dropped it on my systems for good. It works most of the time, but it's still too much of a hassle to do it twice a year in my opinion. I prefer either stable releases with 2+ years of support or full-rolling like Arch.

1. upgrade 1 release behind, so when F41 is released, I'll migrate to F40.
2. the day the migration path fails and troubleshooting doesn't work, I won't bother with Fedora anymore. No fresh install!
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: MX Permanent Secure Upgrade Path?
I suppose if it was "easy" do develop and integrate into MX the devs would have done it already, since yes, it would be a pretty nice tool in the MX toolkit. The "problem" with an upgrade tool like that is probably, that you'd need to develop it every 2 years almost from scratch and hard-code a lot of it, since it had to consider all of Debian's release-specific design changes.
If it ain't broke, don't fix it.
Main: MX 23 | Second: Mint 22 | HTPC: Linux Lite 7 | VM Machine: Debian 12 | Testrig: Arch/FreeBSD 14 | Work: RHEL 8
Main: MX 23 | Second: Mint 22 | HTPC: Linux Lite 7 | VM Machine: Debian 12 | Testrig: Arch/FreeBSD 14 | Work: RHEL 8
Re: MX Permanent Secure Upgrade Path?
And everyone's system is different. I don't see how the devs can guarantee trouble-free in-place upgrade for every user.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: MX Permanent Secure Upgrade Path?
As an honest person, I always say my opinion, which I know sometimes it is not nice! The end Linux user is the one that makes the choice, and distrowatch is an indication!Eadwine Rose wrote: Tue Jul 23, 2024 12:57 pm Why should we be more competitive? That is not the goal of MX. It's not a race after all :)
If your case is solved, and you want to help other users, click on the Solved-Button on the top right of a user's post.
Don't forget a system backup!
Don't forget a system backup!
- anticapitalista
- Developer
- Posts: 4297
- Joined: Sat Jul 15, 2006 10:40 am
Re: MX Permanent Secure Upgrade Path?
Because it is not possible to guarantee success as there are too many variables to consider.an easy permanent and secure upgrade, why not
I actually upgraded antiX on this laptop I'm using from antiX-17 to antiX-19 > antiX-21 and antiX-23.
Each time was not easy as I had to fix various broken packages each time I upgraded.
In the end, I wiped the final upgrade as there were issues I could not fix that was causing boot delays and the desktop was not 'snappy'.
I started with a fresh antiX-23 and now I'm glad I did as the issues were not present.
A point and click UPGADE NOW app would be a disaster IMO
anticapitalista
Reg. linux user #395339.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - lean and mean.
https://antixlinux.com
Reg. linux user #395339.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - lean and mean.
https://antixlinux.com
- FullScale4Me
- Posts: 1086
- Joined: Fri Jan 08, 2021 11:30 pm
Re: MX Permanent Secure Upgrade Path?
An in-place major version upgrade of ANY current OS that completes without ANY minor issues is a Unicorn. I've never seen it in my 37 years in IT!
With the 'Preserve Home' option in the MX Installer and coupled with the User Installed Packages tool one can get to >95% completion of a fresh install easily WITHOUT the cruft of old files that can/may cause issues.
What's left in that 5%?
IMHO the developers of MX Linux have never been in any competition for such an OS as you describe. If a user wants an OS with both guard rails AND training wheels there is always that Linux OS with a name that sounds like candy :-)
I agree 110% Well said!CharlesV wrote:The method outlined here to 'install fresh" and then reinstall the applications that you had on the old system (or as many as possible.), is about the best possible solution... and the devs have thought through and created a very good process to minimize the pain of 'reinstall'. Using the MX User Installed Applications tool can really help cut through most of the pain. And the devs have made the installer save and carry your data and configs to the new install. (as outlined in the MX Install docs)
Reading and working with the install this way... provides one of the best 'upgrades' I have seen for linux.
Agree. IMHO the other distros that do NOT give any such caution are doing a disservice to their newbie users.asqwerth wrote:For now, I believe that the in-place migration/upgrade path provided is going to remain advice that comes with a caution/warning.
+1 There is ample evidence to support this in the forum, such as requests for help after an upgrade failure.MadMax wrote: ...If you're feeling adventurous you can always go for the inofficial in-place upgrade which works similar to Debian's regular upgrade procedure, but be prepared that it will probably take longer (i.e. troubleshooting something) than just reinstalling it anyway...
With the 'Preserve Home' option in the MX Installer and coupled with the User Installed Packages tool one can get to >95% completion of a fresh install easily WITHOUT the cruft of old files that can/may cause issues.
What's left in that 5%?
- Themeing and backgrounds
- Flatpacks
- Appimages
- Other hand action changes (WiFi logon, VPN, boot options, etc)
IMHO the developers of MX Linux have never been in any competition for such an OS as you describe. If a user wants an OS with both guard rails AND training wheels there is always that Linux OS with a name that sounds like candy :-)
Michael O'Toole
MX Linux facebook group moderator
Dell OptiPlex 7050 i7-7700, MX Linux 23 Xfce & Win 11 Pro
HP Pavilion P2-1394 i3-2120T, MX Linux 23 Xfce & Win 10 Home
Dell Inspiron N7010 Intel Core i5 M 460, MX Linux 23 Xfce & KDE, Win 10
MX Linux facebook group moderator
Dell OptiPlex 7050 i7-7700, MX Linux 23 Xfce & Win 11 Pro
HP Pavilion P2-1394 i3-2120T, MX Linux 23 Xfce & Win 10 Home
Dell Inspiron N7010 Intel Core i5 M 460, MX Linux 23 Xfce & KDE, Win 10