![](https://lemmy.ca/pictrs/image/33f22615-aa41-4fbd-9c09-d635020f2233.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Figure out the uid/gid (numeric) for the user in lxc, then change the data permissions to those.
Figure out the uid/gid (numeric) for the user in lxc, then change the data permissions to those.
User-serviceable switches would be so nice…
Deep fried AI.
The patients or their families don’t even get the gift card, that goes to the hospital.
They do have a bpf sensor. It’s still shite, managing to periodically peg a CPU core on an idle system. They just lifted and shifted their legacy code into the bpf sensor, they don’t actually make good use of eBPF capabilities.
If the sensor was using eBPF (as any modern sensor on Linux should) then the faulty update would have made the sensor crash, but the system would still be stable. But CrowdStrike has a long history of using stupid forms of integration, so I wouldn’t put it past them to also load a kernel module that fucks things up unless it’s blacklisted in the bootloader. Fortunately that kind of recovery is, if not routine, at least well documented and standardized.
Use -m
and limit the build job’s memory so it doesn’t kill the docker daemon.
The London Underground is actually kind of a dumb use-case because it’s fixed infrastructure.
On the other hand it’s a perfect test bed, because there’s sufficient changes of direction and speed, and the fixed infrastructure lets you measure drift. Plus it being underground helps simulate GPS signal being weak or unavailable.
You can, but you’ll need to increase the microwave’s power accordingly.
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.
It has implications on the effectiveness of VPNs on public networks.
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.
GM had at one point been working on an eCrate block for conversions, but they seem to have abandoned it.
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.
Brian Kernighan. Got the chance to have lunch with him!
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.