this post was submitted on 25 Aug 2025
90 points (80.4% liked)
memes
17022 readers
4264 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This may seem like too much work, but it guarantees an all-or-nothing procedure. If some package is broken, the entire upgrade process is canceled, and the system remains in the state that it was.
I have had a couple of partial upgrade cases on Arch. It was not fun live booting to repair it, every time this happened.
I've had updates fail on NixOS. A kernel update didn't generate the initramfs and the system wouldn't boot. Booting to a previous generation and reapplying the update fixed it.
This is very rare, though, and unlike Arch can be fixed without a Live USB.
This sounds like a bug on Nix configuration, or the kernel build process.
If NixOS had caught the error, you wouldn't have gotten a faulty generation at all. This is different from pacman/apt/dnf, which will happily continue the upgrade, resulting in a broken system with no easy way to fix it.