Haha. Popos gnome doesn't have this. You get a pop up and says 60s count down. Wish I knew what command that is. I usually have hotkey 'poweroff' and that ista kills everything and shuts down lol
Ich verstehe das Thema nicht. In DACH kommen Themen, die für den kompletten DACH-Raum relevant sind und in Deutschland die, die Deutschland betreffen, aber nicht Österreich oder Schweiz.
Artikel über Deutschland-Themen sollten auch alle in der dortigen Community sein. Viel zu häufig kommt es zu irrigen Situationen, dass. Der Bundesrat etwas beschließt und ich mit denke "Hä, what?" und dann erst später merke, dass es der schweizer ist, was mich null tangiert. Andersherum weiß ich nicht, ob ein Artikel über die bayrische Hochschule und der Verbindung zur Bundeswehr die Schweizer so brennend interessiert.
Ein Sammelsurium ergibt null Sinn, außer dass es nach mehr aussieht. Wo sind die Argumente dafür, alles zu mischen?
Und die These mit den Abos ist eher falsch. Ich habe Communitys abonniert und habe die Spezialcommunitys, da mich der Rest nicht interessiert, also bspw. kein DACH, weil zu viel Zeug, das für Deutschland uninteressant ist.
Bot-Spiegelung? Nein, wo Mehrwert. Wer tagesschau-Artikel will, soll auf tagesschau gehen. Das hier ist ein Community-Forum, kein leerer News-Replikator.
Both Windows and Linux have their respective SIGTERM and SIGKILL equivalents. And both usually try SIGTERM before resorting to SIGKILL. That's what systemd's dreaded "a stop job is running" is. It waits a minute or so for the SIGTERM to be honoured before SIGKILLing the offending process.
I once spent several angry hours researching zombie processes in a quest to kill them by any means necessary. Ended up rebooting, which was a sort of baby-with-the bath-water solution.
Zombie processes still infuriate me. While I'm not a Rust developer, nor do I particularly care about the language, I'm eagerly watching Redox OS, as it looks like the micro kernel OS with the best chance to make to it useful desktop status. A good micro kernel would address so so many of the worst aspects of Linux.
Performance is the major flaw with microkernels that have prevented the half-dozen or more serious attempts at this to fail.
Incurring context switching for low-level operations is just too slow.
An alternative might be a safe/provable language for kernel and drivers where the compiler can guarantee properties of kernel modules instead of requiring hardware guarantees, and it ends up in one address space/protection boundary. But then the compiler (and its output) becomes a trusted component.
RedoxOS would likely never become feature complete enough to be a stable, useful and daily-drivable OS. It's currently a hobbyist OS that is mainly used as a testbed for OS programming in Rust.
If the RedoxOs devs could port the Cosmic DE, they'd become one of the best Toy OS and maybe become used on some serious projects . This could give them enough funds to become a viable OS used by megacorps on infrastructures where security is critical and it may lead it to develop into a truly daily drivable OS.
Zombie processes are already dead. They aren't executing, the kernel is just keeping a reference to them so their parent process can check their return code (waitpid).
All processes becomes zombies briefly after they exit, just usually their parents wait on them correctly. If their parents exit without waiting on the child, then the child gets reparented to init, which will wait on it. If the parent stays alive, but doesn't wait on the child, then it will remain zombied until the parent exits and triggers the reparenting.
Its not really Linux's fault if processes don't clean up their children correctly, and I'm 99% sure you can zombie a child on redox given its a POSIX OS.
Zombie processes are hilarious. They are the unkillable package delivery person of the Linux system. They have some data that must be delivered before they can die. Before they are allowed to die.
Sometimes just listening to them is all they want. (Strace or redirect their output anywhere.)
Sometimes, the whole village has to burn. (Reboot)
SIGTERM is a graceful request to the application to terminate itself and despite their names kill and killall default to SIGTERM (also useful to send other signals to processes, like START, STOP and NOHUP).
Yeah, no. Windows is the easy starter but the more you get experience, the more you fight the system.
Or you go the Linux approach and set your tooling up from start via third-parties from Chocolatey/Scoop.Guess the red line represents this.
kbin.zerstoererbande.de
Heiß