Skip Navigation

Posts
46
Comments
166
Joined
2 yr. ago

  • Basically, you can open some widgets inside a standalone window instead of attaching them to a bar/desktop, making them act like some kind of standalone application instead - including losing all their state as soon as their window is closed.

  • Personally using Dex, it's about as lightweight as you can get, it can be configured with a single configuration file on disk, and it runs entirely stateless as well.

    It only deals with authentication delegation though, unlike larger systems like Keycloak.

  • We're moving towards more btrfs - or at least LVM+

    <other FS>

    where there's no btrfs support - on as much of our server fleet as we can, since the lack of snapshotting on the other filesystems is making consistent backups way too expensive resource- and time-wise.
    With LVM it's at least possible to take a block-level snapshot - which is really inefficient compared to a file-level snapshot, but it at least provides a stable point for backups to run from, without having to pause all writes during the backup or risk running out a sliding window if allowing writes to continue.

    For a home user (especially one who's not as well versed in Linux or don't have tinkering time), I'd personally suggest either ext4 - since it's been the default for a while and therefore often what's assumed in guides, or btrfs where distros include it as a default option - since they should be configured with snapshots out of the box in that case, which make it much harder for the system to break due to things like unexpected shutdowns while running updates.

    I'd personally stay away from ZFS for any important data storage on home computers, since it's officially not supported, and basically guaranteed never to be either due to licensing. It can remain a reasonable option if you have the know-how - or at least the tinkering time to gain said know-how, but it's probably going to be suboptimal for desktop usage regardless.

  • Oh I am more than capable of complaining about both. Like RedHat again fucking over the community and making our life even more troublesome, or the electronics software company using the RedHat ESR duration as their release timeline due to support requirements for their certifications.

  • I definitely agree with your second point, but unfortunately there are big software companies which don't.
    The main software package which we have to use for our electronics courses only supports RHEL as one example - and currently only RHEL 7 at that.

  • I work as a Linux sysadmin for a university, we're paying for a full RedHat site license with all the goodies, and we certainly feel royally screwed over by this.
    Not every single piece of software we run is a RedHat developed/sanctioned thing, and the removal of a guaranteed bug-compatible development platform for the people building those pieces of software - without jumping through hoops or limiting development efficiency - mean that we can no longer guarantee that core pieces of our infrastructure software will remain available for our RHEL installs. Not to mention course IT, where things are even worse in that regard. Lots of such software is already developed/tested/packaged on Alma/Rocky, and if they start diverging from being RHEL bug-compatible - which is very likely with this change - then we're going to either have to switch away from RHEL - and the paid support, or lose support from the pieces of software.

    We're probably going to have to move a bunch more of our ~1.4k systems off of RHEL and onto things like SUSE, Debian, etc in the near future, just so that we're ready for when shit really hit the fan.