Every day. There's no point being an a bleeding edge distro if you're not riding the edge 🤣
The horror of rebooting every day.
I shut everything down at the end of the day. Takes <30 seconds to boot up so it's not really an issue
It takes about ten seconds. Thirty or so if you include all my running programs restarting
every 7 days
Or if I hear about a security update.
That's what I'm doing as well, seems like a good compromise.
Infrequently (when I remember)
When I think of it. Every few days on average, sometimes weeks though.
I've blindly updated a year+ old Arch install without introducing problems. Not saying they don't ever happen, but it isn't that common.
Whenever I'm bored and can't think of anything else to do
When I remember, or when something breaks
Counter-question: how do linux releases roll?
Daily, or on machines I don't use daily, every time I boot into it
Generally as I get a notification that packages are available. The exception is probably if there's a new kernel and I don't feel like rebooting.
I usually run updates every night before I shut down my computer. Probably in part a leftover from the time I used Gentoo and I'd leave my computer on over night compiling updates. I'm not saying this is the optimal way, it just feels right for me.
Daily usually.
I update Portage almost daily but do the actual package updating kind of every week - it depends on how many packages are (or how big they are) to be updated
Every day by cronjob.
Every day (NixOS unstable)
Every few days on the machines I use daily, but I have a couple spare laptops which I only use infrequently, and I usually don't run into any major problems when I have to make a big set of updates on a machine I am using for the first time in a few months.
twice or thrice a day. i have seen problems happening if you wait more than week (signatures not matching and stuff). Also I have a mostly automated setup (essentially sudo password read from password manager into std input of sudo -S sh -c "yes | pacman -Syu ", yes command will update the packages.) since i manually trigger it, if i know i do not have internet or not in a situation to deal with it in case something goes wrong (last happened more than 2 years ago), then i do not. I also see the command's output which lists all packages updated, so if there is something that requires reboot, i will reboot soon.
Once a week and only when I have time to potentially fix something that breaks. Usually because of something I did. Nobody told me I'd have to deal with config file changes in etc. Pacnew in my case. Had to discover that on my own.
Using diff with meld makes it pretty simple. I missed a line in one file recently and SDDM stopped automatically starting on boot. Growing pains. Plus I threw myself in the deep end to learn faster with a rolling release but that's just how I operate.
Part of me welcomes breakage because that's how I got gud at bending Windows to my will as a kid.
Exceptions of course if there's a new feature I want to try out ASAP.
Once a week
Every week or so
Linux Questions
Linux questions Rules (in addition of the Lemmy.zip rules)
- stay on topic
- be nice (no name calling)
- do not post long blocks of text such as logs
- do not delete your posts
- only post questions (no information posts)
Tips for giving and receiving help
- be as clear and specific
- say thank you if a solution works
- verify your solutions before posting them as facts.
Any rule violations will result in disciplinary actions