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.
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. 😞
The problem there is the word “Manjaro”
Unfortunately while they market themselves as beginner friendly that’s simply not true
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
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
My Windows is more like “I am scheduling the restart. Pray I don’t schedule it any sooner.”
Mine will do the restart and boot into Linux.
Windows Updates are always like that. Halfway through it’s got to restart, bootloader picks Linux, Windows doesn’t get to finish the other half of its update til the next time it’s chosen.
You can configure Grub to boot into whichever entry you last selected. Makes rebooting much more convenient
you know you can make it so the last used OS gets booted right?
Is Linux higher in your boot priority?
Linux is higher in any priority.
When I had a dualboot, that’s how I ordered it.
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.dstraight to jail
Yes, let’s keep this community family friendly. I could do without such obscenities.
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.
I am one of lucky 10 000 Thanks
Same
same here!
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.
I am not sure how Windows handles processes, but on Linux you have different signals.
SIGKILL(9) generally kills the process immediately, but there are other signals likeSIGTERM(the default signal, 1) which asks process to gracefully quit, and many others.If you want to know more, check the
signal(7)man page or this Wikipedia page.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.
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’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?
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 0turn 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 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.Yes, in this
commandone liner, the system should not power off when the update took too long.Or is
yessomehow supposed to take care of this?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.
ya’ll aint just pulling out the power plug?
I flip the breakers so I can keep the power plug connected
I flip the breaker whenever it’s time to shut down.
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.
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.
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.
