Linux is slow at killing apps when you run out of memory because it was designed to also run on low spec hardware even if very slowly (making the ui totally unrensposnive) due to swapping.
This comic is about the kill command, how Linux kernel is handling force stopping apps vs (old?) Windows when if App frozed it was hard to close it. Now with modern apps and hardware you very rarely see that as most apps are designed to have asynchronous logic that is correctly handled, but it's still more or less relevant.
Funny :)
Hard to be sane with so many broken hardware implementations... 😅
Cudos for the Linux developers!
I call those estimates BS like always, but who knows.
Maybe they should focus on giving people a way to access those legally? Where on that poster campain say where to go? And secondly... They as always still introduce the BS regional locking!
It first downloads all packages from net, then it proceed totally offline starting by verifying downloaded files, signatures, extracting new packages and finally rebuilding initramfs.
Because arch is replacing the kernel and inittamfs in-place there is a chance that it will not boot if interrupted.
This issue was long resolved on other distro.
One way to mitigate it is by having multiple kernels (like LTS or hardened) that you can always pick in grub if the main one fail.
Old good factorio headless Penguin, it's like that for so long...
Hello fellow Factorio players :)
Because Nginx Proxy Manager exists.
And also because for me it started from web hosting where Apache and Nginx dominate and later because of many easy to understand example configs from the net including many "docker letsencrypt" examples.
You can go to /var/log/apt/ and read the history.log as it will contain every single package that you did install/remove.
Based on that you can just restore it to working state by manually undoing the changes (removing installed, installing removed)
Only [ Confirm ] and [ Set later ] in the dialog? No way to never set/change/cancel? Rapist mentality?
don’t run any commands that you don’t understand. Ask it to break down any commands it tells you to run if you don’t understand them.
You need to pay extra attention to this, as ML models will spit out commands and parameters that doesn't exists if there was not enough examples in training dataset for that action. Especially with explain as it could just spit out totally wrong but "sounding good" explanation for parameter etc as it not always will tell the magic keywords like "typically" that indicate that it doesn't have confidence as it's "based on other similar command/knowledge".
In your example it spit out:
-m: Prune empty directory chains from the file-list.
--prune-empty-dirs: Exclude empty directories that result from the inclusion/exclusion pattern.
which is actually exactly the same parameter with 2 different explanations, you can confirm this with man rsync
--prune-empty-dirs, -m prune empty directory chains from file-list
So the more edge case you have the bigger chance it will spill out bad results, but those new models are shockingly good especially for very common use cases.
This should be illegal, companies should be forced to open-source games (or at least provide the code to people who bought it) if they decide to discontinue it, so people can preserve it on their own.
PHP Fatal error: Unparenthesized a ? b : c ? d : e is not supported. Use either (a ? b : c) ? d : e or a ? b : (c ? d : e)
Linux running X11 has 2 clipboards:
Normally both those clipboards work independent as they are handled by 2 different processes, so you can for example copy one text using ctrl+c and copy another text by only selecting second text, then you can paste both, one with middle click, second with ctrl+v
More and more distro have a clipboard managers that have a feature to "sync" both clipboards, but it's a lot of time disabled because it's more confusing people and sometimes annoying. Why it's confusing and disabled by default? Imagine that you selected some text, then did a ctrl+c, you move to some word document, select text, remove it, and want to Paste it. Guess what, the selecting you did to remove text did copy the selection to clipboard overriding what you did have there from ctrl+c.
Most if not all terminal emulators (konsole, gnome-terminal, xterm) support both clipboard styles, old-school select to copy, and new one but because the "ctrl+c" shortcut reserved to stop/interrupt applications they all decide to use ctrl+shift+c to do a copy. And yes, not only terminal emulators use ctrl+shift+c, I did have few encounters on some random apps, but most of the time, if ctrl+c is used for something else, ctrl+shift+c was available.
“There are only 10 types of people in the world: those who understand binary and those who don’t.”
https://www.exploringbinary.com/there-are-10-types-of-people/