sudo reboot, that way the gui gets to die in a fire, too!
To the people complaining Windows has an aggressive method. Sure but I didn’t know about it till now. Task manager didn’t make it obvious to me and so I didn’t know about it till now (and everyone keeps talking about commands and shutdowns so it doesn’t even sound like you can do it through task manager). Linux’s system manager did and I have known about it since first using Linux (about half a year ago now)
Are you sure your currently updating?
YES DO AS I SAY!
user@debian> |
REISUB. I own you machine, and you will do as I say. Reboot.
Windows: Has a complex and graceful shutdown process to make sure programs never close if there’s a problem with them and your computer just stalls on shutdown until you hold down the power button and completely void out the purpose of the graceful shutdown.
Ever tell a pc to shut down and come after work and it’s still waiting for click a box.
Closing correctly means the program stops NOW
one of my favourite things when i switched to linux first was using the meta+Q hotkey to shutdown a program (this was with PopOS i think). with windows there is alt+F4 but some programs only use shift+alt+F4 which makes it a lot more confusing. on top of all that if youre using a laptop then its another keypress for the Fn key in some cases
kill commands make one feel like a Caesar
et tu, Sudo?
Kill ‘em all, let God sort ‘em out 🤣
Lol yes. Killall makes one feel like a god.
i mean
I just use scissors, I have so many IECs laying around
I like it. Simple but effective.
Great way to damage a power cable.
Old wives’ tale. I’ve only ever yanked power cords out of the wall and I’ve yet to have one go bad on me.
The type of case that plug has in the stock photo is not coming apart without extreme violence.
My ex: what charging cables do you have? They last forever, mine break after a year!
Also my ex: so I got a bunch of the same charging cables you have and they all broke after a year
We should start clamping little handles to them.
Kill commands make me look like a CS:Go Civilian
Laughs in Sierra
elaborate please
old sierra DOS games, uh, they fucked up the code when exiting so they’d just crash. so they changed the error code to say “thanks for playing Kings Quest” or something similiar
You literally kill/xkill/killall the program.
In As400, you type PWRDWNSYS *IMMED.
Then you pray it comes back up in a timely manner.
Linux is actually great if you need to implement graceful shutdown with signals – I love it all around :)))
Don’t both GNOME and KDE send sigterm first on shutdown?
Yeah, this meme is bullshit but gets still posted every other month or so. Windows can also just kill a process, similar to sigkill.
I don’t mind a bullshit meme, most memes are bullshit. Sometimes the bullshittery itself is the funny bit, or to put it another way, there are times like this where the absurdity of it is what’s funny to me. Like, Linux’s kill levels operate, as they must, as advice to the running process, because the os has no insight or capability as to how to gracefully close a process - nor should it. It’s an impossible task to know what safe cleanup looks like. But I like the image of the Linux penguin shooting Firefox tbqh
Is this even true? I am fairly sure that Linux also has a graceful shutdown process, but I’ll admit I haven’t looked into it.
yeah we have SIGTERM for graceful and SIGKILL for not so graceful shutting down a process.
In order of decreasing politeness: 1, 2, 15, 9 = HUP, INT, TERM, KILL = “Please stop”, “Quit it”, “I’m warning you” and “BANG”
9 kills all 9 lives is they way the hpunix guy explained it to me in the mid 90s
This is put so beautifully!
Hup is frequently just “hey, reread your configuration files and keep going”
True. I think of it more as a semantic shift. In the old days, processes would actually quit and some other process would resurrect it as necessary, but then someone had the idea of having some processes catch the HUP and do all that itself without actually bothering any other processes.
And the implementation might actually involve an
execof the process’ own executable, meaning that it actually does self-terminate, but it leaves a child in its place.
