Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)JO
Posts
2
Comments
351
Joined
4 yr. ago

  • It’s everything after the install I don’t have time for. The install is the easy part. 😆

    There are distros which are semi-rolling (Fedora) or rolling (Tumbleweed) which make it easy to maintain the install without lots of configuration.

  • My list overrated list additions:

    • Ubuntu: They break shit, it’s half baked, snaps, and Canonical is really into vendor lock in.
    • Arch: I really have better things to do then baby sit my install.
    • RHEL: Containers were created for reasons, and one of them was RHEL.
    • Any Linux without systemd or glibc: Mistakes were made, and then different mistakes were made trying to prove systemd made mistakes. Musl based Linux distros are going to have compatibility problems, so I might as well run a different OS. The BSDs are *nix-like systems without glibc with a history and larger communities.
  • Since the OP specified server hardware, probably not. RH said RHEL wasn’t going to support anything which didn’t use UEFI to boot, and Arm specified UEFI in their ServerReady hardware certification.

  • They’re spot on. I had this thought last week while trying to find an ISO. It’s like it’s a state secret or something. 😆

    Fedora, OpenSuse, Arch, Gentoo, Kali, and Armbian all make it easy to find an ISO or image to get started. The free RHEL downloads are the only thing more hidden then Debian downloads.

  • Why should you care? Tech diversity is good, and people can try out different approaches. Aside from that, there’s not a reason. Systemd is a really good desktop init.

    What is init freedom? It means the init system can be changed without other software breaking because there is a dependency on some functionality of the init. In this case, a dependency on systemd. Although it’s probably a dependency on a subproject under the systemd umbrella rather then systemd itself.

    Why systemd? It’s tailored to weirdnesses in the Linux kernel. The Linux kernel isn’t perfect, and it’s user land isn’t tied to the kernel. Systemd is a shim which papers over the oddities. I don’t remember which oddities, but they’re there and people ignore them.

    Were there dumb decisions made? Yes, especially for the server side. I should test out some other inits for servers, but it ultimately works fine.