No, they can’t think and reason. However, they can replicate and integrate the thinking and reasoning of many people who have written about similar problems. And yes, they can do it must faster than we could read a hundred search result pages. And yes, their output looks slightly better than many of us in many cases, because they are often dispensing best practices by duplicating the writings of experts. (In the best cases, that is.)

https://arxiv.org/pdf/2508.01191

https://arstechnica.com/ai/2025/08/researchers-find-llms-are-bad-at-logical-inference-good-at-fluent-nonsense/

I though they’re why the desert racists box spread so far to the north.

Often known as the “Gartner Hype Cycle”

GlusterFS is (was) really cool, but I would not set up a new instance. It used to have significant support and development from RedHat, but they decided to halt their work on it, and focus on Ceph.

GlusterFS is getting a few slow updates from some alternate developers, but I would only count on that being fixes for current installations.

Yes, many bad ideas are possible to implement. At least temporarily. Until the next cleanup process figures out how to remove cadvisor dir regardless of file contents. Or the next OS release turns /tmp into a ram disk. Or… or… or…

Yes, it’s a fun academic exercise to think through possible mitigations. And in the end, it will still be dumb to keep this in /tmp

Why wouldn’t changing to permissions keep the file from being deleted by the internal process?

That’s like keeping your lunch laying outside on the sidewalk, getting stepped on by people and destroyed, and then wondering if your lunch would be safer if you put it in a stronger bag (but still left it on the sidewalk).

Don’t leave your lunch outside laying on the sidewalk, regardless of what you might do to “protect” it. Don’t keep important files in /tmp