This is so IRL. It was the last drop in the bucket when using systemd, when it started to let me wait out a countdown every time I shut it down. I would just flip the power supply switch. Then I switched from Arch to Artix.
this post was submitted on 27 Jul 2025
547 points (99.5% liked)
unix_surrealism
2947 readers
1 users here now
one should not chase the electric dream
A place to share original content related to computers, content, surrealism, wizardry and everything else.
founded 2 years ago
MODERATORS
It’s fun to watch that countdown with a non-removable laptop battery that is about to die. Problem solved it’s self I guess. Edit: Alpine Linux now.
I was pretty sure systemd doesn't have to be configured like that. Anyway, on my company managed Linux systemd tries to access some network service on startup and shutdown. Unless I'm plugged into on site LAN, I get to wait a full network timeout (presumably with retries) every time.
At least it's not Windows.
probably just because it's doing the correct thing and waiting for the applications in your session to close?
In principle, but it did never hurt anything when I just straight up cut the power so I got the feeling that I was waiting for nothing. It wasn't like the disk wasn't flushed yet or anything. Maybe it is good to be extra careful when restarting a server or something similar, but for desktop usage I prefer if the init system just kills everything after a few seconds so I can go with my day. Neither is right or wrong just whatever you prefer. I like a cutthroat style in general and I accept the minor risks that come with it.
It's not a good practice to allow immediate shutdown on a PC, as long as the OS doesn't do checks for finished data transfers. You will lose data if SSD is not finished writing it. Yes, even with super fast SSD there might be stuff that takes seconds to complete.
yeah makes sense ig, i very frequently long hold the power button when i have to deal with w*ndows
the system is going down for shutdown NOW!
Whether the system likes it or not
@CsXGF8uzUAOh6fqV @NoFood4u fuck systems with timers on shutdown
I want it to respect my acpi events
I meant it when I pushed the button
The command is shutdown -h now
Personally I prefer poweroff
Please notice: some exceptions do apply. For example bpap cpap and respirators
No, there are no exceptions. If the power button is pressed, it should shut down and cease drawing power immediately. If it's so critical that it can't be shut down safely, don't include a power button, and add a battery for backup purposes.
My old btrfs system auto defragging while shutting down (and taking too long): I guess I'm going to die
Btrfs ate my data a few times a long time ago.
ZFS: Not even once
is that a bumpmap or cosmic background?
The background is made from a plain purple color with added HSV noise. Then an effect is added on top of everything by copying the entire image into a new layer and applying a convolution with a kernel like this:
-1 0 0 0 0
0 -1 0 0 0
0 0 1 0 0
0 0 0 1 0
0 0 0 0 1
In GIMP those are under "filters > noise > HSV noise" and "filters > generic > convolution"
In some cases please use a hammer to terminate the process correctly.
This is me telling the waffle iron it brought death upon itself by not having a true off switch as I pull the plug from the wall.
Haha, kitchen appliences that don't have a poweroff button are actually what inspired me to draw this. It was a coffee machine in my case.
At least the kitchenaid has a lever to yank to a stop. But that waffle iron! Oh he annoys me! But at least he's not connected to the wifi so he can't defy orders...yet.
My fridge does not have an off button, does that count?
A fridge is never just sitting idle, what reason is there to ever turn one off instead of unplugging?
What about batteries (capacitors?)
Arguably that's not a "machine".
shutdown --poweroff now learned this today from man shutdown