Vivaldi would have definitively enjoyed speed metal.
Vivaldi would have definitively enjoyed speed metal.
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.
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.
Yeah, I can sleep through a fever, but I’ll wake up every few minutes if I can’t breathe through my nose.
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.
Regulation won’t work, because regulation moves slowly, and these companies find workarounds fast. And as long as the cost of breaking the rule is less than the benefits of doing so, it’ll be “just the cost of doing business.”
Use -m
and limit the build job’s memory so it doesn’t kill the docker daemon.
Goes to show how low the bar is that the ADL failed to meet.
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.
citizens government.
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.
My first reaction when reading “jam resistant” was “what, like raspberry?” I think I’ve watched Spaceballs one too many times.