six figures for a junior programmer, no less

ECS/EKS: The ocean belongs to someone else.

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.

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.

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

hides Lennart Pottering dartboard while everybody’s distracted

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.

You are describing a state of software development that has existed since the introduction of punch cards.

Practically every business I’ve worked at has had some internal library or repository of commonly used behavior that can be included in day to day projects.

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.

PHP is better than Javascript these days.

Fucking PHP.

The only thing JS really has going for it is ease of execution, since any browser can run your code… though the ubiquity of Python is closing that gap.

You are not alone. I am here with you.

Subscribe

And his sister, the famous arsonist Anita Mcburney.

Ok that’s just not true at all.

Core temps ramp up astonishingly fast on RPi!

ducks

“Test suite”?

You should know that not all clients display your display name, some only show your username@instance.

It’s not apparent to everyone that your name is Onno.

There is no original thought.

A friend of mine had some explaining to do when he screwed up a dhcp config change and started routing his guest wifi through his “personal” pihole instead of the restricted guest one (he had family/children over often and did not want to be the reason nephew Timmy got an eyeful of wet bush or a beheading).

His family-friendly pihole was at holypi.lastname.local and his private one was creampi.lastname.local

The other poster said it’s about convenience but that’s not really true. The claim to fame for NVMe drives is speed: While SATA SSDs can theoretically run at up to 500 MB/s, the latest NVMe drives can hit 7000+ MB/s.

It’s for this reason that you should pay attention to which NVMe drive you choose (if speed is what you’re after). SATA-based M.2 drives exist – and they run at SATA speeds – so if you see a cheap M.2 drive for sale it’s probably SATA and intended for bulk storage on laptops and SFF PCs without room for 2.5" drives. Double check the specs to be sure what you’re getting.