Maybe it fails because you are trying to solve a problem with a configuration when it should be solved by a function implemented in the program you are trying to use.

I don't consider swap to be emergency RAM storage. I know that the kernel will decide by itself to use swap even if it has plenty of available RAM and the swappiness threshold is not reached.

Nevertheless, my two decent laptops (one with 16 GB RAM, the other with 64 GB RAM) never swap, even with Docker Swarm and multiple stacks, multiple VMs, desktop activities, and gaming.

It's been a while since I last saw a physical machine actively swapping.

I understand that some limited hardware may need swap, but I can't see such hardware having a GPU with plenty of VRAM.

That said, hacking things is always fun :)

Edit: Typo

Wars are always bad news and robot wars are very bad news. Many countries will fall into an endless war economy.

I know this is very 20th century, but it helps a lot to understand how everything fits together and to remember what each tool does in a complex stack.

Documentation is not always perfect or complete, but it makes it much easier to find parameters in config files and know which ones to tweak.

And when the documentation falls short, the old adage applies: "Use the source, Luke."

Basicaly an EDR

I should have added, "and every data returned by the agent must be considered harmful".

You should not trust anything done by an agent on the behalf of someone and certainly not giving RW access to all your data and credentials.

In any case, the data that will be provided to the agent must be considered compromised and/or having been leaked.

My 2 cents.

You will never have a UI capable of encompassing all the settings available in Linux. You will only have a UI capable of configuring your desktop experience, which is just a small subset of the full Linux experience.