Hacker News new | ask | show | jobs
by the_wolo 152 days ago
It seems to me that MS has started to vibe code Windows. It's so surreal that they managed to kill the shutdown program. I mean: this 1 simple program worked for 30 years no probs doctors hated this trick but idk
3 comments

Just to point, but there's nothing simple about shutdown.
And hence under no circumstances one should ship a code that just doesn’t do what it’s supposed to do in the first place, we know the cloud doesn’t use it much, but c’mon it’s a critical part of the system.
D'oh sudo shutdown

Linux: I give a damn about you're super critical nuclear reactor loading up, this computer is going down NOW

Systemd: “A stop job is running for User Manager for UID 1000 (1s / 2min)”
Ctrl-Alt SysRQ, Pause, o (off) for that.
Well it is still shutting down
It would actually be sudo shutdown -h now. Otherwise it waits a few minutes for the control rods to drop before it shuts off the coolant control.
That still does stuff like unmounting filesystems (which can take a minute with snap, if they haven't fixed it), you can go further with the (rather unsafe) SysRq key "o", which tells the kernel to shut down without any preparation.
That's quite interesting, considering that -h flag is usually related to showing help.
From what I understand, the shutdown command is actually what is still working.
> MS has started to vibe code Windows

Started ? The chances of Shutdown (from the menu) working in Windows are about 90%.

And then there is the computer who won't stay asleep. I find my PC running about once a week after having it sleep the night before.
I've had the opposite problem with laptops. There's like 3 different menus to configure sleep-on-idle but none of them actually let you disable it even if they claim they do.

They don't even share the same state and can be set to conflicting values, with the oldest looking one usually taking priority.

Disabling screen timeout is even worse since there's additionally the screensaver settings to muddy the waters.