whenever something is broken
You update your broken system to fix it.
I update my working system to brake it.
We might be the same
Update my mesa drivers mid-game? Yea fuck it why not
we are not the same
xbps-install -Su usually when a regular xbps-install <package> fails due to cert issues every few months
And then, inevitably:
but “yay” already does that
Yay ; flatpak update
At most once per day. Sometimes I can go three weeks without remembering to upgrade
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’ve been using
yayfor 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?
To be honest, it’s just what I’ve been using since I switched to Cachy half a year ago. There was no conscious decision made between yay or paru.
I think Go and Rust are both great languages, but there are apparently some speed benefits from using rust/paru. That’s not anything I can factually confirm, just what I’ve heard.
Googling it, it just seems like yay but in rust and it shows PKGBUILD by default. Still cool to find alternative tools though
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.
as someone who is a dev by trade I update/backup on fridays because I think it’s funny.
It’s always funny, until that one day where it isn’t
PC-LOAD-LETTER, wtf does that mean?!
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.
It means you need more paper.
Once a day
I do
sudo pacman -Syuas 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.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.
When I am bored. A few times per month in winter. Once or twice per summer.
We are still talking about updates, right?
Yes, why?
Just to be sure
Are you sure?
not really…
Under Arch, I was stalling system upgrades for around 1 and 1/2 weeks, otherwise had a lot of library issues. This also ensure that I can install software, programs and dev libs pretty easily.
Under gentoo, I update my package DB every 2 or 3 weeks, then merge changes. Usually, I do this on monday. Working from sources, with a fixed package DB, makes things really stable.
Right now, my main workstation runs OpenSuse. I upgrade every 2 weeks.
Servers are mainly running OpenBSD and stable software. Around 2/3 weeks.
I also follow Sec Lists and Software Update feeds. If something urgent shows up I do upgrades and merges in a 12h period.
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.
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.
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.
