$ pacman -Syu
$ sudo !!
Umm… yay -Syu
Just ‘yay’
yay -Syu --develYou don’t need the
-Syu, it’s the same asyay --develSomething new every day, I’m prone to assuming
pacmanand by extensionyaywill do weird things if I don’t have the correct number ofus andis.man yayIf no operation is specified ‘yay -Syu’ will be performed
It has been this way for years. RTFM.
Fun fact jackass, new people start learning these tools every single day.
Every damn time! That’s why I started aliasing ‘sudo pacman -Syu && paru’ to ‘U’
make a cron job.
I alias it to fuck to remind me of the appropriate reaction
until grub shits itself
systemd-bootbabyCan’t have grub problems if you don’t have grub. The howto is great, I’ve converted a few machines using it without any (subsequent bootloader-related) issues.
refind master race
yay yay yay
every 15 minutes
Did that, arch broke, installed arch again lol
I put this in my taskbar which helped me stop running paru habitually.
I run it every time I power on my laptop. Just can’t help it.
On the opposite end here. I know if there’s a kernel update then I’d need to reboot and restart everything.
Only to activate the new kernel! You can just leave the current one running with minimal issues, even less if you have something like KernelCare live patching security bugs
Any dynamicly loaded module will fail. Just reboot.
Assuming any dynamically loaded module will fail, why does KernelCare exist and why is it used so prevalently in web hosting environments? It costs money, so buying it when it doesn’t work seems odd.
Very valuable high uptime servers exist but they take care, as in professional admins, to maintain it.
None of this applies to Arch or home users. You get full kernel updates and no old modules are kept. You reboot.
Other distros like Fedora keep old versions around but you still have to reboot to get updates.
I still haven’t restarted my system since updating to 6.4
I unironically do that
Guys what are you talking about, pacman is a cheese with a ghost problem
Sudo Pac-Man -Sy
thats me
Is there a safe way to do uodates automatically? I could store my password in plaintext and thats barbaric but it still doesnt fix the problem that packages and dependecies can break during updtaes without user input if im right. Tho i guess you could write a script that automatically looks for updates and notifies the user.
deleted by creator
The task is objectively unsafe. Both live updates are unsafe and require intervention but also Arch does not guarantee updates require no manual tasks.
You can set up a Cron job or systemd timer for the root account to run that command regularly, if it is a non-interactive command!
System updates aren’t something I’d really trust to be non-interactive.
I’ve never had to interact with system updates in Linux distros beyond saying “yes I want to update” in the last decade. If I didn’t want to, there’s usually a force update flag available to skip the asking part. Would I do this for a server without backups? Absolutely not. For home use? I’ll roll the dice; I have backups even if there’s a couple days of shipping time to get all 12TB mailed to me.
Of course, major distribution releases are a different monster. Fortunately, I don’t deal with those often and when I do, I migrate instead of upgrade.
Ah, I forget sometimes that I’m in a general linux community and not the arch community.
I run arch, btw.
Which I think is why I have a different attitude about this, the rolling release system can occasionally cause snags. I haven’t had any of the major chaos that other people will warn you about, but I have had some oddities relating to shifting dependencies or upstream changes. I’ve had one or two things refuse to update citing mandatory manual intervention.
yay
guilty as charged
God I miss apt, why would I not want to run
-Syu?I use manjaro btw
sudo pacman -Syuis equivalent tosudo apt-get update && sudo apt-get upgrade, you’d want to run it about once a day to ensure you have all current updates. Pamac should allow you to update everything from a GUI, so you don’t have to worry about that.Cool that’s what I thought, just confused by the people saying they’ve bricked their systems by doing it!
Packages get updated a lot in arch. Occasionally a package may push an update with a big that can cause major problems. Often times those bugs are fixed relatively quickly, but if you update too often, you are more likely to update to a package with such bugs.
is that an excuse?
