You guys do updates ?
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?!
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.
Just a few weeks (months?) ago:
Replace package nvidia with nvidia-open? [y/n] Y
Queue having to redo all my previous work to get the integrated graphics card and the dedicated graphics card playing well with each other
deleted by creator
A lost fedditor?
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
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?
Googling it, it just seems like yay but in rust and it shows PKGBUILD by default. Still cool to find alternative tools though
I like typing yay and getting updates.
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.
I doubt that speed in a package manager would depend greatly on programming language choice. A package manager downloads the repository index, evaluates your current environment, decides what packages you need and then downloads them. You may get minor speed improvements due to a more performing programming language, but we’re talking about milliseconds differences in a process that likely takes several minutes. I wouldn’t take that into account when choosing across options. Indeed speed can greatly vary across package managers, but that mainly depends on implementation; as such you may have a package manager implemented in a slower language that is faster than one implemented in a faster language.
If I have to choose a package manager, I wouldn’t even consider speed and rather evaluate functionality. I don’t know paru, I imagine it allows doing what yay allows doing and as such I’d be satisfied with either of them.
And then, inevitably:
but “yay” already does that
Yay ; flatpak update
topgrade
*paru
whenever something is broken
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…
Once a day
Once a yay
yay every day
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.
At most once per day. Sometimes I can go three weeks without remembering to upgrade
every 5 minutes sounds about right
If I’m bored and done with everything and can peacefully restart
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.
Yeah, that’s fair. It might be possible to get incompatible versions between two different tools that interact with each other, if say one shuts down and then starts up with the new version but the other doesn’t shut down and stays on the old.
sudo pacman -Sybau
sundays
