No. It will boot the previous kernel, but the user experience will be at least suboptimal if some packages have already been removed during the upgrade, but the upgrade stopped at some point because a downloaded package was corrupt, leaving lots of dependent packages unconfigured. In case networking doesn’t work, it’s also inconvenient to manually download the affected package on another machine and transfer it with a usb stick onto the computer to restart the upgrade.
Assuming you enter your password upon running sudo, isn’t there the risk of sudo’s privilege timing out if pacman takes too long to complete? I believe I tried something similar, intending to run a one-liner I could start then walk away from. However, I ended up returning to see the system not rebooted hours later.
Or is yes somehow supposed to take care of this? Sorry, newish Debian user here who hasn’t ventured outside the distribution much.
The command after && runs only if the previous command returns non-error exit status (0), if pacman returns error the latter command won’t be executed.
Additionally there’s probably a configuration option for sudo for it to not time out, but it doesn’t matter since you can just use systemctl reboot as a normal user to reboot your system (at least on Debian). If that’s too long I recommend to add this to your .bashrc (if you use Bash): alias reb='systemctl reboot' or something similar.
Maybe this is just a yay thing but I think if sudo priveleges run out while downloading the files it prompts you for your password again before performing the changes. That would lead to it either trying to use the yes output or getting stuck in the password prompt, only failing in the prior.
This entire problem could be solved by just running it as the root user.
There’s no timeout for sudo. When permitted, a process runs as root and then closes.
Also, the system will still shutdown when update fails because pipes do not care if previous commands exit with a nonzero code, unless pipefail is set.
I do
yes | sudo pacman -Syu && sudo poweroff(Update and poweroff)
Fuck that noise
sudo shutdown 0turn off NOW bitch!I prefer shutdown now gives me a feeling of power
“&&” will only run shutdown if the update runs correctly.
I do “;” to definitely run the shutdown after the update process exits. (Don’t want to keep the system running if nothing is happening any more.)
I do “|” so it updates and shuts down at the same time
If you’re able to successfully boot the machine afterwards is not your concern?
what’s fun in a successfully booting system? we are arch users for a reason!
Well, as I’m using Debian, maybe I’m a more cautious type.
I don’t know about arch but my system usually boots fine after an upgrade. (Gentoo here)
If the update is successful. If there are failures in critical steps, well…
Doesn’t it roll back to a previous state then?
No. It will boot the previous kernel, but the user experience will be at least suboptimal if some packages have already been removed during the upgrade, but the upgrade stopped at some point because a downloaded package was corrupt, leaving lots of dependent packages unconfigured. In case networking doesn’t work, it’s also inconvenient to manually download the affected package on another machine and transfer it with a usb stick onto the computer to restart the upgrade.
You don’t need sudo to run poweroff on Arch, provided there’s no other users logged into the system
And it’s a login shell.
Assuming you enter your password upon running
sudo, isn’t there the risk ofsudo’s privilege timing out ifpacmantakes too long to complete? I believe I tried something similar, intending to run a one-liner I could start then walk away from. However, I ended up returning to see the system not rebooted hours later.Or is
yessomehow supposed to take care of this? Sorry, newish Debian user here who hasn’t ventured outside the distribution much.The command after
&&runs only if the previous command returns non-error exit status (0), ifpacmanreturns error the latter command won’t be executed.Additionally there’s probably a configuration option for
sudofor it to not time out, but it doesn’t matter since you can just usesystemctl rebootas a normal user to reboot your system (at least on Debian). If that’s too long I recommend to add this to your.bashrc(if you use Bash):alias reb='systemctl reboot'or something similar.Maybe this is just a
yaything but I think if sudo priveleges run out while downloading the files it prompts you for your password again before performing the changes. That would lead to it either trying to use theyesoutput or getting stuck in the password prompt, only failing in the prior.This entire problem could be solved by just running it as the root user.
Yes, in this
commandone liner, the system should not power off when the update took too long.No,
yesis simply answering all questions asked during the update procedure (start upgrade, replace config files, restart services) with “yes”.There’s no timeout for sudo. When permitted, a process runs as root and then closes.Also, the system will still shutdown when update fails because pipes do not care if previous commands exit with a nonzero code, unlesspipefailis set.Edit: i’m blind.