this post was submitted on 12 Mar 2024
400 points (96.5% liked)
Technology
59534 readers
3195 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I love that on my arch setup, I update every single day, usually more than once, and doing so almost never requires me to powercycle my computer.
There is occasional weirdness if you don't powercycle though. In particular, certain KDE updates will make the desktop misbehave until you reboot. I get where you're coming from though. Quick updates and the ability to decide when you want to restart means that I have no qualms about updating frequently.
I am on Arch too and
pacman -Syuis usually a snack I have with my morning tea.If the desktop misbehaves, just restart the desktop (log out and in again)?
You can log out, then CTRL + ALT + F1 , log in and run the update command. If there was no kernel update, you don’t have to reboot. If some service got updated restart the service (if that was not done by the updater.) Then you can switch back to the graphical session usually by CTRL + ALT + F7) and log in again.
Problem with this is that it's really hard to figure out whether some update to some minor library is going to affect an application. Sometimes you don't even know which applications are using that library.