Bro The RAID Fuckin Sucks

That surgeon general’s warning sent me into a giggle fit.

No. Symlinks and hardlinks are two approaches to creating a “pointer to a file.” They are quite different in implementation, but at the high level:

• Symlinks can point to other filesystems, hardlinks only work on the same filesystem.
• You can delete the target of a symlink (or even create one that points at nothing), but a hardlink always points to a real file.

In both cases, the only additional data used is the metadata used for the link itself. The contents of the file on disk are not copied.

I don’t necessarily agree with it, but there’s the third option of just disabling SELinux and removing the frustration entirely.

No, but you’ll have much more overhead. I have a VM that hosts all Docker deployments which don’t need much disk space (most of them)

This is a big point. One of the key advantages of docker is the layering and the fact that you can build up a pretty sizeable stack of isolated services based on the same set of core OS layers, which means significant disk space savings.

Sure, 200-700MB for a stack of core layers seems small but multiply that by a lot of containers and it adds up.

• When you’re trying to make it level and hit the studs with your fasteners, it’s much easier with a stick than a whole cabinet carcass.
• Cleats make the cabinet easy to install and remove.
• French cleats have a substantial amount of bearing surface and are extremely stable as a result, even without additional fasteners.
  • That said, for a cabinet I would probably still drive a screw from the inside through the back panel into the cleat to eliminate any chance of a strong bump from underneath knocking the cabinet off the cleat. You know, like when you drop that last m4 nut on the desk and it bounces into the corner and you have to reach over your project and soldering iron and cup of coffee to retrieve it and then stand up too quickly in triumph and bang your head off the underside of the cabinet…

Sovol is another option, decent quality out of the box and their corexy units are stupid fast.

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?

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.

how do I delete someone else’s comment?

You

I thought about it ANURA right, they probably just don’t remember.

Here’s the only thing you need to know: radio is black magic.

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).

I think the usual recommendation these days is get the highest rated corexy in your price range.

I’ve heard mixed reviews about Bambu AMS; seems cool enough, not quite the same as a true dual extruder, has some quirks and annoyances.

There’s Finamp, a music client for Jellyfin with offline playback. I’ve not used it personally yet, but with Spotify ratcheting up prices again I’m in the process of switching to self-hosting my music library. When that’s up and running it’s at the top of my list for Android clients.

Subscribe