LOL
LOL
LOL
It's a screenshot of a screenshot in a video? What's that shield?
Ah I completely forgot that it was a separate extension, I only use it in smarttube 😂
It's a screenshot of a video that I did
You did the screenshot, or the video? Or both?
Windows after pressing shutdown and update: you wanted to use me still right????
Shutdown isn't shutdown anymore, so it has to reboot for the updates. After the reboot, though, there's no longer a shutdown pending.
Just do sysrq+s, sysrq+c (triggers panic) and flip the power switch for instant power off.
goddamn generation loss-ass meme.
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
me turning off the power supply: (i didn't have anything open so hopefully it's fine...)
It's much less risky than it used to be. Journaling filesystems reduce the risk of filesystem corruption to near zero and are fairly ubiquitous now on non-removable media.
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
Yes, let's keep this community family friendly. I could do without such obscenities.
system deez nuts
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.
This is just not true.
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?
I am one of lucky 10 000 Thanks
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.
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?
Yeah, I was thinking that. I wish we had a button (other than power off) to stop the service immediately.
Mine suspends immediately.
I do yes | sudo pacman -Syu && sudo poweroff
(Update and poweroff)
Fuck that noise sudo shutdown 0
turn 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
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?
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 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
yes
somehow 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".
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. 😞
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.
Debian was a horrible choice actually, my laptop's WiFi card didn't have a kernel driver available at the time. Tracking down the correct one was an interesting journey by itself, getting it compiled and loaded was another. In my 20 years of Linux experience I've compiled my fair share of drivers from source, but this thing was a complete disaster and simply refused to work.
I even tried Ubuntu (still feel dirty about that one): also no support out of the box.
So I needed a rolling release, as kernel support would drop fairly soon. Being downstream from Arch I reckoned any major issues will be worked out in Manjaro before hitting their release.
So far I'm actually quite happy with it, my only gripe is the stability of Pamac. The frontend tends to hang during updates from time to time or require a manual database update to show available updates again.
And of course the issue with packages not building anymore, until you clear the build cache. The (bi-) weekly reboots because of kernel updates are annoying, but something I can live with.
Or Mint
The problem there is the word "Manjaro"
Unfortunately while they market themselves as beginner friendly that's simply not true
ya'll aint just pulling out the power plug?
I flip the breakers so I can keep the power plug connected
I take an axe to my power meter. I want everything shutdown.
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 don't really, I just use Linux
Fair. I have two identical PCs. One is Win10, the other is Mint. Saves on figuring out dual-booting.
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.
for the most part i don't care, but really, all those fucking terminals i left open, i know they're open, that click per window of yes close has never been helpful
I used to override that setting.
I...uh...learned some uses for it.
I bet there were interesting uses.
I won't say i've never shut down a long running process, but i've gotten a lot better at not running them adhoc in a terminal :)
The program 'btop' is currently running in this session. Are you sure you want to close it?
i'll prob just start running pkill konsole before shutdown. was thinking of pkexec /sbin/shutdown -h now on a button, but it is kind of nice having some of my apps recover on reboot.