I don’t have a Fedora workstation in front of me right now, but it memory serves me right there’s a “default applications” or similar menu in Gnome’s settings.
I don’t have a Fedora workstation in front of me right now, but it memory serves me right there’s a “default applications” or similar menu in Gnome’s settings.
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.
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.
So TCP ACK is the backwash?
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
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.
I used to be a teaching assistant at university, and never sorted by name. But based on my experience I don’t think it’s frustration that accounts for the disparity, it’s that as you see more and more assignments you start getting a feel for common issues and are able to point them out more easily. I would always do two passes because of that to ensure that I normalized the weight of my marking.
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.
I will never forgive JSON for not allowing commas after the last element in a list.