The other responses have so far talked about hardware setup, so I’m not going to do that. Instead I’m looking at your software setup: VMs can be comparatively power inefficient compared to containers, specially for always-on services that idle often.
I have my SD docked into a 4k monitor most of the time, and I can tell you with certainty that some games will struggle at 4k on the SD. You can still use the 4k monitor for them, just play at a lower resolution.
Does registry still have that problem of making it practically impossible to do garbage collection on old images?
I will never forgive JSON for not allowing commas after the last element in a list.
If I had a nickel for every time in the past week I saw an article about a courier game I’d have two nickels. Which isn’t much, but it’s odd that it happened twice.
Yeah, you’d have a LoadBalancer service for Traefik which gets assigned a VIP outside the cluster.
virtual IP addresses
Yeah, metallb.
Or the classics of symphonic metal like Stratovarius.
The container is reproducible. Container configuration is in version control. That leaves you with the volumes mounted into the container, which you back up like any other disk.
It’s not that Seagate improved (which it may have), it’s more that WD has noticeably declined. It’s not a race to the bottom (yet), but there’s effectively no competition any more, so they aren’t incentivised to improve quality.
Figure out the uid/gid (numeric) for the user in lxc, then change the data permissions to those.
Since FF 6 and 7 have already been mentioned, I’m going to give a honorable mention to Shining Force.
Use -m and limit the build job’s memory so it doesn’t kill the docker daemon.
rapid mitosis
As in you are seeing multiple boot entries? It’s likely one entry per kernel version that you have installed. It doesn’t happen often these days any more, but in some situations it’s handy to be able to revert to a previous kernel if for example third party modules break.
Yep, if you request the desktop version you don’t get that redirect.
Or just request the desktop version.
28 Days Later, Cockneys vs Zombies
Not sure about erasing all of it, but it is (or was) certainly possible to delete enough of it to brick a motherboard https://www.phoronix.com/news/UEFI-rm-root-directory
I don’t know where you got the idea that I’m arguing that old versions don’t get new vulnerabilities. I’m saying that just because a CVE exists it does not necessarily make a system immediately vulnerable, because many CVEs rely on theoretical scenarios or specific attack vectors that are not exploitable in a hardened system or that have limited impact.
Are they going to be binning those too?