virtual IP addresses
Yeah, metallb.
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.
When I was younger and more naïve, I used to think a case was useless. I kept my phones in my pocket most of the time, and didn’t feel particularly clumsy or reckless. Then I got a phone that happened to have a glass back, and it broke not because I fumbled it, but because it slid out of my pocket onto time floor while I was sitting down. Glass backs on phones are bullshit.
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.
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
Not sure what you are talking about. Paragraph 1 has
The malware is delivered through a fake Google Chrome update that is shown while using the web browser.
and the article makes it pretty clear after that that the user is tricked into installing the fake apk.
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.
For me Hyperion ended up giving me the closest out of the box experience to what I wanted.
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.
To be fair though, the chance that every Lemmy instance goes down at the same time is so much lower than Reddit going down. Sure, my instance might be unavailable, but I’d be able to hop onto the next one and continue.
What’s the scale? It might be a passable seafood fork.
Yeah, you’d have a LoadBalancer service for Traefik which gets assigned a VIP outside the cluster.