I kinda botched the first --emptytree world.... I'm on my second now
and a clear pattern is emerging...
dev-cpp
│ └── abseil-cpp-20240722.0
That is causing cascade failures into protobuf, marble, opencv and
almost surely others.
The problem is that it was written in C++. In order to write C++ you
need to live for 7 years in a monestary high on a mountain. By the
middle of the second year, most programmers realize there is no point,
come down from the mountain, finish the project in C to great acclaim,
before the 7 years are up too!
These developers spent only six years and six months on top of the
mountain and played it fast and loose with the compiler too and, used
types in ways that the previous compiler let them get away with but the
current one doesn't....
Anyway I'm going to reboot my computer and start the process of finding
a combination of kernel and Nvidia drivers that actually works. =|
I'm running kernel 6.10 right now and it has this bizzare obsession with
cache, it will exhaust a pool of 400gb of physical ram as cache until
the machine gets choked, forgetting what the point of cache was (hint:
It's not to choke the machine by consuming all ram!!!) and force the
user to manually get the damn thing to clear all of it. This happened
after only two months (and change) of uptime which is ludicrous... I
shouldn't have to do a damn thing for six months... This is the problem
which prompted me to go through the agony of trying to upgrade to newer
versions with more bugs, less support for the things I actually know how
to use, slower, with more build errors, but newer... Yes, newer is the
only thing that matters...
Look at this!!! I cleared cache only 4 days ago and it's already sitting
on 224 GB of cache!!!
KiB Mem : 52765632+total, 26441356+free, 44915076 used, 22483510+buff/cache
--
You can't out-crazy a Democrat.
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
