lemmyng

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?

Yeah, you’d have a LoadBalancer service for Traefik which gets assigned a VIP outside the cluster.

virtual IP addresses

Yeah, metallb.

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.

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.

The fact that you think it’s not possible means that you’re not familiar with CVSS scores, which every CVE includes and which are widely used in regulated fields.

And if you think that always updating to the latest version keeps you safe then you’ve forgotten about the recent xz backdoor.

Just because it has a CVE number doesn’t mean it’s exploitable. Of the 800 CVEs, which ones are in the KEV catalogue? What are the attack vectors? What mitigations are available?

You did a recursive chown or chmod, didn’t you.

Bazzite, as a gaming-first distribution, makes some choices that are acceptable for such a platform, but that I believe are unacceptable in a secure development environment. This is why I wrote “not ideal” instead of “bad”. If you don’t care about security then it’s perfectly cromulent. But I value security, so I would not recommend it.

Bazzite is a good HTPC or living room gaming distro. It is not an ideal all purpose desktop distro, just like a Steam Deck is not an ideal all purpose desktop system.

If you want a Bazzite-like experience that is better suited for the desktop then use Fedora Silverblue, which is what Bazzite/ublue builds upon.