406
LOL
(anarchist.nexus)
goddamn generation loss-ass meme.
me turning off the power supply: (i didn't have anything open so hopefully it's fine...)
On my work PC I disabled automatic restarts and I'll just hibernate it for weeks at a time, keeping my work stuff open. Convenient, and I can install updates when I choose to.
Windows just randomly installing updates only when I'm working on something with a customer.
one of the reasons I'm moving away. pisses me off so much at work, I don't even want it at home
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 horrible, but these days Windows updates actually give me less issues AND require less reboots than Manjaro. ๐
If you want something easy, you can install one of the "Just Works" distros. Even though Manjaro advertises themself as beginner-friendly, they certainly are far from it.
Debian and PopOS are both great choices.
Or Mint
The problem there is the word "Manjaro"
Unfortunately while they market themselves as beginner friendly that's simply not true
I like how you censored systemd
People need to learn that it's ok to say systemd on the Internet and stop self censoring
Let's not get carried away. Fuck and shit are ok, but I draw the line at s*****d
~~init.d~~ straight to jail
Yes, let's keep this community family friendly. I could do without such obscenities.
This is just not true.
- Linux does have a graceful process.
- Windows's process is not graceful
Yeah and in linux when you say "kill this process" that process fucking dies. No 10 minutes of windows trying to negotiating with a crashed program to close. No I'm not angry about this happening to me at work today, why do you ask?
Both Windows and Linux have ways to gracefully ask a program to close and to force close it. Not being able to select the correct one on either system is a skill issue.
And when chrome freezes rest of the desktop goes gray and everyrhing else freezes too including the task manager.
I had such an issue with Teams on Mac the other day. It had a phone call stuck running in the background, so I tried to Quit the app. The Quit Teams option just turned gray, and the laptop even refused to reboot.
Managed to wreck my NVMe drive with an unsafe shutdown on linux the other week, gave it a few hours for the self check, booted back into the distro and has been running fine ever since.
Pretty sure windows would've just set the computer on fire at this point.
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
Linux is so strong I turn it off from the power button. Saving 5 seconds.
That's weak. I always pull on the power cord until the plug comes out. That shuts it down in a second flat.
I was talking about a laptop with non-removable battery of course! I turn off my desktop via Zigbee remote hooked to Home Assistant which flips a Zigbee power switch that the AC power cord is hooked up to. Even faster death than going under the desk and unplugging the power cord. Even just unplugging itself takes time.
Iโm a little spoiled by this. I did it on Windows and had to rebuild the boot partition.
That random systemd service waiting 1.5 minutes.
You all not suspend/hibernate?
Mine suspends immediately.
I do yes | sudo pacman -Syu && sudo poweroff
(Update and poweroff)
"&&" 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 ";" to definitely run the shutdown after the update process exits.
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...
You don't need sudo to run poweroff on Arch, provided there's no other users logged into the system
Fuck that noise sudo shutdown 0 turn off NOW bitch!
I prefer shutdown now gives me a feeling of power
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.
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.
view more: next โบ
this post was submitted on 27 Aug 2025
406 points (100.0% liked)
linuxmemes
26991 readers
1254 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