ace

joined 1 year ago
[–] ace@lemmy.ananace.dev 46 points 1 month ago (4 children)

The predictable interface naming has solved a few issues at work, mainly in regards to when we have to work with expensive piece-of-shit (enterprise) systems, since they sometimes explode if your server changes interface names.
Normally wouldn't be an issue, but a bunch of our hardware - multiple vendors and all - initialize the onboard NIC pretty late, which causes them to switch position almost every other boot.

I've personally stopped caring about interface names nowadays though, I just use automation to shove NetworkManager onto the machine and use it to get a properly managed connection instead, so it can deal with all the stupid things that the hardware does.

[–] ace@lemmy.ananace.dev 8 points 2 months ago (2 children)

Factorio is great, I'm also a fan of X4.

[–] ace@lemmy.ananace.dev 1 points 2 months ago

It's somewhat amusing how Itanium managed to completely miss the mark, and just how short its heyday was.

It's also somewhat amusing that I'm still today helping host a pair of HPE Itanium blades - and two two-node DEC Alpha servers - for OpenVMS development.

[–] ace@lemmy.ananace.dev 0 points 8 months ago* (last edited 8 months ago) (1 children)

Flatpak uses OSTree - a git-like system for storing and transferring binary data (commonly referred to as 'blobs'), and that system works by addressing such blobs by hashes of their content, using Linux hardlinks (multiple inodes all referring to the same disk blocks) to refer to the same data everywhere it's used.

So basically, whenever Flatpak tells OSTree to download something, it will only ever store only copy of that same object (.so-file, binary, font, etc), regardless of how many times it's used by applications across the install.
Note that this only happens internally in the OSTree repo - i.e. /var/lib/flatpak or ~/.local/share/flatpak, so if you have multiple separate Flatpak installations on your system then they can't automagically de-duplicate data between each other.

[–] ace@lemmy.ananace.dev 0 points 8 months ago (4 children)

A lot of that data doesn't actually exist, ostree hardlinks data blobs internally, so the actual size on disk is much smaller than most disk usage tools will show.

[–] ace@lemmy.ananace.dev 0 points 11 months ago (1 children)

RHEL is going hard on XFS, they've even completely removed BTRFS support from their kernel - they don't have any in-house development competency in it after all. It's somewhat understandable in that regard, since otherwise they wouldn't necessarily be able to offer filesystem-level support to their paying customers.

Though it is a little bit amusing, seeing as Fedora - the RHEL upstream - uses BTRFS as their default filesystem.

view more: ‹ prev next ›