Linux is so strong I turn it off from the power button. Saving 5 seconds.
this post was submitted on 27 Aug 2025
447 points (94.1% liked)
linuxmemes
27012 readers
1201 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
Iβm a little spoiled by this. I did it on Windows and had to rebuild the boot partition.
load more comments
(2 replies)
That random systemd service waiting 1.5 minutes.
You all not suspend/hibernate?
load more comments
(2 replies)
I do yes | sudo pacman -Syu && sudo poweroff
(Update and poweroff)
You don't need sudo to run poweroff on Arch, provided there's no other users logged into the system
load more comments
(1 replies)
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.
load more comments
(1 replies)
Yes, in this ~~command~~ one liner, the system should not power off when the update took too long.
Or is
yessomehow supposed to take care of this?
No, yes is 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, unless pipefail is set.~~
Edit: i'm blind.
load more comments
(2 replies)
ya'll aint just pulling out the power plug?
I flip the breaker whenever it's time to shut down.
One thing I've seen my computer do a few times: log me out, by itself. Some rare times I try and unlock back into my session, my current open and active user with my programs running, and instead I am greeted not by my desktop as it was when I locked the screen, but rather the lock screen as it was before I even logged in the first time around
Y'all don't delete WSUS, block all of the M$ IPs at both your HOSTS file and your router, and stop all update processes?
Do you even know how Windows works?
I thought the Windows update system is actually not too bad. At least compared to Mac.
Yea, it has a robust rollback system, which is part of why it takes so long now.
But... I only do updates a couple times a year to minimize the headache on my personal machines.
My work machines it's not my problem, but I reboot them at night a couple times a week, just in case.
Compared to Mac? Macβs is so much better? The number of times windows has fucked me over by updating on a restart.
Fair enough. My experience on Mac has been pretty bad compared to Windows but to be honest there could be recency bias there. I use Mac every day for work and don't use Windows very often but at least Windows has never suddenly closed all my apps because it decided it was time to update.
I think you got lucky then, windows is known to do exactly that. Well, these days it at least gives you a warning that it will do it in 15 minutes or so.
load more comments
(2 replies)
Meanwhile:
My W11 Pro PC: I'll wait installing my monthly updates until you give me the okay. And I'll wait for the reboot until you say so.
My Manjaro laptop: sorry, I couldn't build package X. Go f*ck yourself while I provide you with no information on how to fix this.
*A manual build cache clear later*: all good! But now perform our weekly reboot.
It's ironic, but these days Windows updates actually give me less issues AND require less reboots than Manjaro. π
load more comments
(5 replies)