That requires GPU passthrough. Totally different ballgame in complexity and experience.
avidamoeba
joined 1 year ago
I use Sensor Reheat. 😎
Labor and infrastructure (also labor) costs money. If you're not paying for it with money, you're paying with something else. In other words you're the product. Since you can't build all of the needed infrastructure yourself, you'll have to pay at least for that. And so at the end of the day you will most likely have to pay more money. It's also possible for someone to be paying for the infrastructure you use. E.g. a small fraction of Lemmy users pay for the infrastructure and software everyone else uses. That only works as long as the ratios are sustainable. A more sustainable scenario is for a large fraction to be paying very little.
The bad news is you'd have to learn more technology and pay more money. The good news is there are decent alternatives.
Seriously, having been hit by a fairly rounded Impreza at low speed that still did significant damage, I'm shivering at the thought of what these edges would do to soft tissue and bone in the same conditions. The pressure at the contact points would be dramatically higher.
Duck DNS
quack 🦆
At this point I think I'm just gonna wait for the patch to land in Ubuntu.
Weird. Reading the issue on GitHub I got the impression that it affects 2.2.0+.
Also I glanced something that the version of coreutils also contributes to the interaction.
E: Seems like Ubuntu LTS is unlikely to be affected a lot due to the older coreutils.
It looks like due to the older coreutils Ubuntu 22.04 LTS is unlikely to be affected as much. So if you're on Ubuntu LTS and have not compiled it yourself, you might have dodged data corruption.
Would this corruption be caught by the checksumming?
No
This is probably outdated. It's from 2018.
Let me tell you about a large bank and two data centers operated using VMware and the type of talent the bank is able to hire and retain. A move away from VMware is a 5-year project involving hiring, retraining, design mistakes, budget overruns, and a lot of grey hair. The year was 2012. 7 years later, one DC converted to OpenStack, the project is shelved and the majority of th OpenStack DC gets converted back to VMware due to "OpenStack disaster."