Then you’re on your own. What the duck 🦆 do you expect to happen if you can’t even invest the 10sec to skim over a message (in the few events that there even is one) to see if it affects you and any manual intervention is required.
A fully functional system, just like any other normal OS?
You hit update - boom - you get one, seamlessly, with no breakages and no other user interaction. And that’s how it works pretty much everywhere - except, you know, Arch.
If you’re fine with it - that’s fine, go ahead and tinker all you like. But don’t expect others to have the same priorities.
Man that’s news from 2016, like, it’s a bit rare occasion, y’know. You’re way more likely to get borked by Arch even after reading all the instructions, and it did happen numerous times.
Touching grass is what I do when you take steps to intervene in your system to make an update work.
I see you are an Arch maximalist, but that goes beyond reason. Even Arch proponents are normally not as aggressive on the topic, and admit Arch is too complicated in that regard.
The only problem here is that snapshots (and btrfs for that matter) are not the default behaviour. I would really appreciate Endeavour having this as the default setup. It is very likely what you’d want.
Yes, Garuda does, even with bootable snapshots, but it’s otherwise not as clean as Endeavour. As far as I can tell, mkinitcpio/GRUB2 or their setup thereof causes more problems than it solves. My system was bricked multiple times until I switched to a dracut/systemd-boot setup, which works flawlessly since quite a while.
As for the user experience, there are 0 distros you should perform a (major) upgrade on without taking a snapshot first. I had broken systems after apt upgrade. From my point of view rolling vs versioned release are basically occasional mild vs scheduled huge headaches.
Arch is easy to install; it’s a headache to manage.
If you want a stable Arch, you need to check the updates and take very granular control over packages and versioning.
While some nerds may like tinkering with their system in all those ways, for regular user Arch is simply too much effort to maintain.
Informant
Useful, but still it kinda makes you read through all the update news, which is…why?
I’d like to just hit update and not bother.
Then you’re on your own. What the duck 🦆 do you expect to happen if you can’t even invest the 10sec to skim over a message (in the few events that there even is one) to see if it affects you and any manual intervention is required.
A fully functional system, just like any other normal OS?
You hit update - boom - you get one, seamlessly, with no breakages and no other user interaction. And that’s how it works pretty much everywhere - except, you know, Arch.
If you’re fine with it - that’s fine, go ahead and tinker all you like. But don’t expect others to have the same priorities.
Yeah just like the FORCED Microsoft updates that broke like hundreds of businesses?
https://www.notebookcheck.net/Microsoft-reimburses-travel-agency-for-forced-Windows-10-update-damages.168378.0.html
Dude go touch some grass
Man that’s news from 2016, like, it’s a bit rare occasion, y’know. You’re way more likely to get borked by Arch even after reading all the instructions, and it did happen numerous times.
Touching grass is what I do when you take steps to intervene in your system to make an update work.
I see you are an Arch maximalist, but that goes beyond reason. Even Arch proponents are normally not as aggressive on the topic, and admit Arch is too complicated in that regard.
You’re just going to shift goalposts every time I’ll post something.
Not recent enough. Not enough cases. That’s different.
And lastly you’ll just claim I do it because I’m an arch maximalist, despite not knowing anything about me :)
It is actually very easy:
3.1) Repeat goto 2
3.2) Rollback goto 2
The only problem here is that snapshots (and btrfs for that matter) are not the default behaviour. I would really appreciate Endeavour having this as the default setup. It is very likely what you’d want.
True, but if snapshots turn from first line of catastrophe response to a regular tool, this is not a good experience.
Also I believe Garuda has enabled snapshots and btrfs by default.
Yes, Garuda does, even with bootable snapshots, but it’s otherwise not as clean as Endeavour. As far as I can tell, mkinitcpio/GRUB2 or their setup thereof causes more problems than it solves. My system was bricked multiple times until I switched to a dracut/systemd-boot setup, which works flawlessly since quite a while.
As for the user experience, there are 0 distros you should perform a (major) upgrade on without taking a snapshot first. I had broken systems after
apt upgrade. From my point of view rolling vs versioned release are basically occasional mild vs scheduled huge headaches.