as someone who is a dev by trade I update/backup on fridays because I think it's funny.
this post was submitted on 31 Jan 2026
598 points (98.2% liked)
linuxmemes
31673 readers
591 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 3 years ago
MODERATORS
It's always funny, until that one day where it isn't
PC-LOAD-LETTER, wtf does that mean?!
e: You guys are making me feel old for not getting this reference: https://en.wikipedia.org/wiki/Office_Space
For those that don't know:
PC = Printer Cartridge (the place where you put ink or paper for it to use)
Letter = 8 1/2 x 11 inch letter sized paper, which is similar to A4
So the message means to load letter sized paper in the printer cartridge, because the sensor says it is empty.
PC in this context stands for Paper Cassette, an old HP term for the paper tray.
It means you need more paper.
load more comments
(1 replies)
And then, inevitably:
I have a script I run daily (named daily) that makes a timeshift backup, checks for updates from pacman, then checks for updates from the AUR. I'm very fond of it :]
Does paru -Syu not also include pacman, or do you just prefer to do pacman first?
I have never heard of paru until this very moment. I will look into it, thanks!
Heck yeah! I hope it helps simplify things!
This might be the first time my limited Linux knowledge has been helpful to an internet stranger. Feels good.
Iβve been using yay for years, and it is sufficient. First time Iβve heard of paru.
Other than being written in rust, how does paru improve the experience of AUR wrapping?
Googling it, it just seems like yay but in rust and it shows PKGBUILD by default. Still cool to find alternative tools though
load more comments
(3 replies)
When I am bored. A few times per month in winter. Once or twice per summer.
I do sudo pacman -Syu as a ritual each time when I start my computer or laptop. Like, the very first thing after the system is booted. So far so good, been doing that for 7 years.
load more comments
(8 replies)
My Debian trixie desktop system rotates /var/log/apt/history once a month. So over the past year:
$ zgrep upgrade /var/log/apt/history.log*gz|wc -l
25
$ ls /var/log/apt/history.log*gz|wc -l
12
$
25 upgrades in 12 months. So about twice a month on average on that one.
At most once per day. Sometimes I can go three weeks without remembering to upgrade
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 thisisunsafe to bypass the error.
It's fucking rough out here.
load more comments
(1 replies)
For me, it's about reducing the amount of time the "update available" icon shows up in the system tray, because its very presence bothers me. Maybe there's something cool and new. Maybe it fixes a severe security problem. If it's for programs I'm not using right now, then the update can be applied right now. Otherwise it's going to have to wait until I'm done. And bother me.
Yes, I could turn updates off and never see it, but that seems like a bad plan in the long run.
Can't you update it all regardless of whether you're using it because the Linux file system leaves the old file intact and just writes a new file and updates the pointer so anything still using the old file carries on as if nothing happened and just gets the update the next time you run it?
This is true. But then I'm not using the latest version while I still have an active session, and that can lead to weird behaviour or errors after the fact.
Case in point, I once received an Xorg update that I allowed to install, but didn't restart the computer properly until much, much later.
By then I'd forgotten about the update, so when I restarted and started having graphics problems, I was mystified.
I've also forgotten how that all panned out, but in the same situation I'd roll back to a previous Timeshift snapshot and work the system forward again until I find the culprit or things are stable, so I assume that's what I did back then.
load more comments
(1 replies)
Once a week usually, or when I have to reboot anyway.
when I have to reboot anyway.
I do the same, then you have these days: "Ok, I'll run a quick update before reboot... Updating qt-webengine?, nooooooo"
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
I've set up unattended upgrades and forgot about updates, until I get a mail saying they happened.
Note that at least on Debian, the unattended-upgrades package only, by default, does security updates. While those are the most important ones, if you want various bugfixes and such, you probably do want to at least occasionally do an update yourself.
On my laptop with LMDE, which is basically Debian, I've configured it to update everything. The only thing left out are flatpaks which I update when I remember.
Fedora Silverblue (actually bluebuild building my own OS)
practically only if there's a new release of a software I want to install (which zeroes out to approx all 2 months)
If Iβm bored and done with everything and can peacefully restart
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 like update && shutdown -P now
And usually in the morning i do another update to check if it missed anything
Run 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 π
every 5 minutes sounds about right
Sometimes I let a Gentoo lapse on upgrades, just for the extra fun.
Every 1-2 weeks, depends on how often I remember
paru -Syu; poweroff most evenings
I use Apdatifier for KDE and it checks every 180 minutes. If there are updates, I update.
Opensuse aeon - I don't do anything. Package manager handles everything
sundays
sudo pacman -Sybau
Usually once whenever I'm on it I'll pull up a terminal and type "yay"
view more: next βΊ