1,138 karma · joined December 29, 2018
Sun (and now Oracle) officially recommended using ECC ever since it was intended to be an enterprise product running on 24/7 servers, where it makes sense that anything that is going to be cached in RAM for long periods is protected by ECC.
In that sense it was a "must-have", as business-critical functions require that guarantee.
Now that you can use ZFS on a number of operating systems, on many different architectures, even a Raspberry Pi, the business-critical-only use-case is not as prevalent.
ZFS doesn't intrinsically require ECC but it does trust that the memory functions correctly which you have the best chance of achieving by using ECC.
For graphics, the same defect could be severe enough to completely render the GPU useless.
The steps described in the article sound familiar to the process done in the early 2000's, but I'm not sure why you'd want to make it hard for yourself now.
I use certbot with "--preferred-challenges dns-01" and "--manual-auth-hook" / "--manual-cleanup-hook" to dynamically create DNS records, rather than needing to modify the webserver config (and the security/access risks that comes with). It just needs putting the cert/key in the right place and reloading the webserver/loadbalancer.
It's a shame JSON parsers usually default to performance rather than correctness, by using bignums for numbers.
AMD has had SEV support in QEMU for a long time, which some cloud hosting providers use already, that would mitigate any such issue if it occurred on AMD EPYC processors.
> This image shows a diverse group of people in various poses, including a man wearing a hat, a woman in a wheelchair, a child with a large head, a man in a suit, and a woman in a hat.
No, none of these things are in the images.
I don't even know how to begin debugging that.
5950x is Zen 3
9950x is Zen 5
How are you measuring complexity?
IPv4 started simple, but had a lot of extensions (literally header "options") to fix and mitigate various issues and underspecified behaviour.
IPv6 started more complex, but had a lot of those shortcomings addressed from decades of experience in the real world.
In the Linux kernel, IPv6 is actually implemented with fewer lines of code than IPv4 (as of 6.12.19, IPv4 = 82kloc, IPv6 = 58kloc).
> standard FSK protocols such as Bell103, Bell202, RTTY, TTY/TDD, NOAA SAME, and Caller-ID
What's more dangerous is that a jury wouldn't know the difference.