That’s not how golf works but I like where your head is at.

I think you mean amanzing.

I’ll see myself out.

What’s blowing my mind about this entire thread is the “rewrite application to support RHEL9” thing I keep seeing. What the fuck applications are y’all running that are so tightly bound to the OS that they can’t handle library and/or kernel updates?

deleted by creator

Ultimately it’s a matter of personal choice and risk tolerance.

The Z1 will be simpler and have larger capacity, but if you have a drive fail you’ll need to quickly get it replaced or risk having to rebuild/restore if the mirror drive follows the first one to the grave.

Your Z2 setup right now can have two drives fail and still be online, and having a wider spread of power-on hours is usually a good thing in terms of failure probability.

I manage a large (14,000±) number of on-site RAID1 arrays in various environments and there is definitely a trend for drives shipped at the same time to fail at roughly the same time. It’s common enough that we often intentionally swap drives out before shipping a new unit to the customer site.

On my homelab, I’m much more tolerant of risk since I have trust in my 3-2-1 backup solution and if my NAS goes down it’s not going to substantially affect anything while I wait for a drive replacement.

Please do not the arch viles.

🌍👨‍🚀🔫👨‍🚀

One of its studies, which was carried out in collaboration with the Charité-Universitätsmedizin Hospital in Berlin, found that breast cancer survivors who took part in the study experienced mental and physical arousal when they used a sex toy.

Filed under “You don’t say?”

how do I delete someone else’s comment?

You

Hey everyone, get a load of this fool drinking from an I ♥️ SYSV mug! Ha!

hides Lennart Pottering dartboard while everybody’s distracted

Mikrotik is pretty decent but their configuration method drives me up a wall. Ansible helps mitigate the annoyance, at least (in that I only have to figure out/remember the arcane incantation for configuring VLANs once, and then subsequently just have the machine do it).

deleted by creator

To add to this, spent fuel is over 90% recyclable. If the US were to instate a comprehensive recycling program like France has done, the spent fuel cache could be reduced to negligible amounts.

If it results in the nuclear plants remaining online and providing energy after the AI bubble pops, that doesn’t seem so bad.

Fission is one of the cleanest energy sources we have today.

Which GPU do you have? I’m looking for an upgrade and those framerates make me drool.

So you’re saying Rust is the TOOL of programming languages.

Point of clarification: DAC is copper, AOC is fiber.

A lot of 10G equipment will support 5G/2.5G SFPs as well, so it can still be beneficial to go 10G on the core equipment.

Ted Ts’o was way out of line in that conference and was clearly channeling his inner ca. 2001 Torvalds.

I think Rust is a better path forward for a majority of the kernel/driver code maintained currently, but it is definitely going to take time for it to gain a foothold. I also think there is some condescension on both sides that is completely unjustified and needs to stop.

The hardline C devs that don’t want to learn Rust need to accept that at some point they will have to either adapt or pass the torch, and that no amount of whining or bitching in public forums is going to change that.

The Rust devs that are getting upset because people are “attacking” their favorite language need to accept that there will be substantial and impassioned resistance to making broad language changes to a set of projects that have existed for decades. It would be an uphill battle for any language to try to supersede C in the kernel; this is not a condemnation or attack on Rust or its zealots, it’s a matter of momentum and greybeard stubbornness.

In fairness, “I don’t want to maintain bindings for a language I never intend to use” is a perfectly reasonable position.

The typical answer here is for the language evangelist to implement and maintain the bindings, and accept the responsibility of keeping them in sync with the upstream (or understand that they will be broken for however long it takes for another community member to update them).