@mycoliza Since you’re using NixOS, you might be able to just build a 2 systems that can mount the new/old pool by name using:
fileSystems."/" =
{ device = "tank/root"; # vary this
fsType = "zfs";
};
# and so forth for all mountpoints
@mycoliza And if things fail to boot for verification, you can reboot with the sata module blacklisted? Or just boot into a recovery and trim the SATA disks before trying again.
@mycoliza@ManishEarth@lunasorcery Eh, seems more like an issue with how rustfmt formats stuff.
To be fair, I do agree that keeping track of "is this still a function call?" can be difficult if you encounter them after a longer closure (or two!), and it’d remain an issue regardless of formatting.
@nick_r_cameron For the latter question, not so much. The `Rust` ABI isn't particularly awesome, but with `Rust` ABI being unstable there’s still hope that using it over any other ABI might produce more efficient code in the future.
@nick_r_cameron `no_mangle` causes symbol collisions when crates get duplicated. If there's an option to avoid using `no_mangle` it is always beneficial to do so. Passing callbacks, calling functions from inline assembly, and similar uses don’t need it for example.
@Android Though to be fair, my take on internet connected vehicles is “they were so preoccupied with whether they could, they didn’t stop to consider whether they should”.
So, uh… Does @Android Automotive mean that 5 y.o. vehicles with it will be running all of them unpatched RCE exploits?
I’m not really finding any support timelines from integrators yet, which suggests “yer on yer own m8” to me.
For more than a decade, memory safety vulnerabilities have consistently represented more than 65% of vulnerabilities across products, and across the industry. On Android, we’re now seeing something different:
https://t.co/X4sxljVN49
Any DDoS reliant on distributed nature would mostly just hit those secondary servers. Yeah, you’ll lose traffic in the secondary markets, but… in the primary market your servers would have a much easier time handling the extra load that could only be characterized as a “meh.”
Idea: could anycast be used by regional websites as a DoS/DDoS mitigation mechanism?
Basically spin up a fraction of servers outside of your primary markets and shovel all your traffic in secondary markets to those servers.
@irevoire @jntrnr @rustlang Did you know you can catch that other issue and have the program continue the execution anyway? Might just work for you too.
@whitequark Not to mention that a hob really rarely stay at peak rated power for extended time. The battery would really start mattering a lot when there are 2+ pans at high heat. And unless there's a cooking technique that involves making charcoal, pans rarely stay on high for long.