I have a bash alias
alias update='flatpak update ; flatpak remove --unused ; emerge --sync -a ; emerge --ask --verbose --update --deep --changed-use --keep-going --with-bdeps=y --backtrack=500 @world ; emerge --depclean ; eclean-dist -d'Which i run likeupdate && shutdown -P nowAnd usually in the morning i do anotherupdateto check if it missed anythingRun the main update before i sleep computer shuts down when done and when i wake up i check what i missed
Does the job every time 😎
My home PC, about once a week, or whenever I have to install new software. My work PC, about once a month because the nvidia driver takes fucking ages to update because of DKMS.
As for the servers under my professional care… it depends. Most of the servers that I made run Debian that I update three times a year whenever the downtime is acceptable for the university (spring break, late summer, early december) or if a CVE needs fixing (e.g. xz-utils). One internet-facing server that I inherited still runs Ubuntu 16.04 because some teachers can’t possibly live without some legacy software and will throw a tantrum if upgrading is even mentioned – that one gets zero updates, and I got the dean’s promise in writing that I wouldn’t be held responsible for it.
The big virtualization server still runs ESXi 6 because the university didn’t want to pay for a lifetime license when it was available, doesn’t want to pay for a subscription now, and doesn’t want the downtime required to fully migrate to Proxmox VE. So it gets no updates. Plus it has a bad SSL cert and I need Chromium’s
thisisunsafeto bypass the error.It’s fucking rough out here.
I inherited a lot of Ubuntu servers at the university, too. But I am not directly responsible which makes life easier; I am just managing it.
Interestingly, they agreed to monthly updates with possible restarts and they are fine with it, because I keep the servers healthy. And: We even plan to move from VMWare hypervisor to Proxmox VE as well, but we can do it in stages without big downtimes.
There is one CentOS server carefully isolated which cannot be updated anymore. Moving it to Rocky would introduce a big downtime and redoing a lot of custom config. Luckily the user-facing server of that cluster is running a current Rocky Linux.
The things, I established so far, are running stable Debian. Nice to see Proxmox VE being based on Debian. (:
It is interesting that you are in a similar boat, but with a different outcome. I hope that your colleguas will reconsider some day.
every week more or less, it’s basically just as often as I remember. oh and whenever I have to update a program for security reasons, like a system wide patch or a new browser release, that sorta thing. using opensuse tumbleweed btw
Sometimes I let a Gentoo lapse on upgrades, just for the extra fun.
maybe once every three or more months
Every 1-2 weeks, depends on how often I remember
When someone reminds me so thanks
Every few days—I seem to have endless libraries that have constant updates.
whenever something is broken
You update your broken system to fix it.
I update my working system to brake it.
we are not the same
We might be the same
Update my mesa drivers mid-game? Yea fuck it why not
For my Manjaro systems, I usually check the forums and after I see a new stable update is posted I’ll do an update in the next few days. Sometimes I’ll check between the big updates for things like browsers or other occasional high priority updates that get posted between the big updates, but usually only if I’m having a problem or have some other reason to do this.
At most once per day. Sometimes I can go three weeks without remembering to upgrade

deleted by creator
A lost fedditor?
And then, inevitably:

*paru
but “yay” already does that
Yay ; flatpak update
Yeah I just have an alias called update that runs all of the update commands, as well as a few other things
topgrade
deleted by creator
Daily, I use Arch by the way












