I find that I habitually open a terminal and run an update on every boot of my system (which gets rebooted once a day). I’m curious what other people do.
You must log in or register to comment.
Usually daily, when I boot up my PC. Unless there’s whole lot of updates, then I tend to wait till the end of the day and my work is done for the day. I mean I can always roll back, but I am weary of issues creeping up over several hours.
Well for my laptop which I use 3-5 days a week (for a few hours at a time) I do it only when I’m at home so it doesn’t get in the way when I need my machine. But I also reboot my laptop every use since with framework suspend just won’t work properly (I’ll look into it soon™).
My desktop I try to update every time I use it but with barely any time and my gaming now happening on my steam deck that’s less and less. Also with the archzfs module I gotta wait for the right timing between module and kernel versions so these days I often miss a few updates.
Multiple times a day, basically whenever I’m bored. Sometimes I get so depressed when there are no updates, that I install some random package or build something from source, so I can look at some text flying across my terminal, and look at all the cool stuff happening on my PC. I also have a
journalct -fandbtoprunning all the time as it’s interesting to see what’s happening behind the scenes.Can I recommend cbonsai and cmatrix?
cbonsai is awesome. Whenever I open a new shell, I have it configured to first run cbonsai so that a bonsai tree is the first thing that I see when I open a terminal.
Thanks for the cbonsai suggestion 😀
Every time I install a package, or once a month.
I use a script that shows new Arch news messages, updates the mirrorlist with the fastest mirrors in my country, updates repo packages, updates aur packages, then prints created .pacnew and .pacsave files as well as orphaned and dropped packages.I use a script that shows new Arch news messages, updates the mirrorlist with the fastest mirrors in my country, updates repo packages, updates aur packages, then prints created .pacnew and .pacsave files as well as orphaned and dropped packages.
Would you mind sharing that script?
It’s not very sophisticated and has no error handling, but I only run it locally…
#!/bin/bash echo -e "\n...READING NEWS...\n" yay -Pw echo -e "\n...UPDATING MIRRORS...\n" sudo cp /etc/pacman.d/mirrorlist /etc/pacman.d/mirrorlist.backup sudo reflector --country Germany --latest 5 --sort rate --save /etc/pacman.d/mirrorlist echo -e "\n...UPDATING REPO PACKAGES...\n" sudo pacman -Syu echo -e "\n...UPDATING AUR...\n" yay -Syu echo -e "\n...ORPHANED PACKAGES...\n" pacman -Qtd echo -e "\n...PACKAGES NOT IN ARCH REPO...\n" pacman -Qm echo -e "\n...NEW CONFIG FILES...\n" sudo find /etc -name *.pac* echo "DONE 😊" #Dependencies: yay, reflector, rsync, noto-fonts-emoji
Exactly the same. My server gets updated whenever I ssh into it, too. And as it also runs on testing repos, it actually makes sense.
Everyday. It is a little bit inconvenient that I’m on Guix, perhaps it would be best if I create a service.
I’m on Guix
Do you mean that you are runnign the GNU Guix distro, or that you are using the Guix package manager on Arch?
I’m using Guix SD. Third-party package managers cannot over the role of system package managers.
Once a week, usually on a Friday when I’ve finished work, usually with a beer
On desktop, once or twice a week, if I think about it.
On my home server, every few weeks or once a month.
On my HTPC :), rarely, since its kind of fragile running Arch ARM on the Radxa Rock 5B. Only when I know there is time to rebuild some required AUR packages to make graphics work again.
Normally when some software I use has a major update. Could be a month, could be a couple days.
I have a script that runs when I start my graphical environment that checks for updates and sends a notification if there are updates. Which prompts me to do a full system update if I get the notification. I shut my PC off at the end of the day and boot it up in the morning, so I update at least daily, occasionally more than daily if I turn my computer on and off multiple times in the day.
I have a script that runs when I start my graphical environment that checks for updates and sends a notification if there are updates.
Would you mind sharing that script?
Literally just
#!/bin/sh if checkupdates || yay -Qu; then notify-send "Package updates available" "To update, press MOD + SHIFT + U" -i "update-catppuccin-mocha" fimod+shift+u was bound to spawn a terminal window running yay -Syu, obviously change the notification to say whatever you want. The icon is a custom icon, replace it with whatever icon you want for the notification or just remove the icon if you don’t want one.
I’ve since moved to Artix so the test is now just
yay -Quascheckupdatesdoesn’t seem to exist on Artix, but if you’re on base Arch and use yay, the above should work. You can also remove the yay if you don’t use yay and I think that just checks for updates from official arch repos, not from aur. (yay -Qushould check both but I have both commands in the script just in case)This is so cool! Very clever solution to this issue. Thank you for sharing! 😊 An interesting thing that I ran into when testing it was regarding the difference between
[] -Quandcheckupdates:checkupdatesshowed that an update was available, but the-Quoption did not reveal the update. It wasn’t until I synced the database with-Sythat-Qustarted showing the updates.Update 2024-03-31T03:20Z: Ah, it looks like
checkupdatesessentially is just runningpacman -Syandpacman -Qu.
Whenever I feel like it tbh. Today I recently had to do so today because of the xz backdoor and before that, the new kde plasma 6 release. Before that, I basically didn’t update unless I needed to.
my desktop, about every other month? i have moved signal-desktop to a flatpak so i don’t have to do a full system update whenever it demands to be updated :D
Usually twice a day on whatever PC I’m runnnig. That is unless I am really caught up in something I am working on then only when that task is complete which is rarely more than a week.
My server about every other day, but if I am traveling I purposefully try not too since I have to be home to debug the worst kinds of situations.
Mostly everyday when I start my computer but I will avoid updating if I have a mission critical project to work on, because arch doesn’t break often but when it does it’s because you were trying to update right before working on a mission critical project.
Pretty much every day, it’s just part of my morning routine when I put the computer on. For reboots, basically whenever something important like the kernel, systemd or pipewire updates, just to avoid weird behavior.
