Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
It does sound like a good idea.
Mid-update you can end up with broken dependencies and thus not fully working system. There may also be a problem with how programs update their config files.
This is especially true with big updates which is why Arch and Manjaro recommended to update from plain TTY during the Plasma 6 upgrade. Reboot, do not login, switch to TTY, stop the graphical login manager, just then proceed with upgrade.
A bit too much to ask for from regular users. Especially since it relies on them reading update announcements before each update.
Personally, I always close most stuff during updates. I even had terminal emulator itself die during update on Linux Mint.
In NixOS you specify whether the update is
switchorbootI always just use tmux with updates and really everything I do in linux