Hello Beautiful community!

I am a student/jr-level IT-guy who has used linux as a daily driver for 2 years now.

I chose Fedora because of it’s similarities to RHEL and RHEL-clone. It was also easy to set up with UEFI and LUKS/LVM, which I somewhat struggled to do on arch. Having wayland, GDM and XDG preconfigured also made starting configuration a lot easier.

When I used arch-based EOS, I usually took the “easy route” when configuring. Instead of using systemd, I just launched stuff on i3-config. Instead of compiling stuff myself I just installed it with aur. Instead of using LUKS or LVM I just had some encrypted directories.

Maybe it was because I was much more experienced when I started with fedora, or maybe it helped to have an already usable system when starting. Either way I feel I learned more using fedora than EOS, even if I heavily modified EOS as well.

However as I am now considering switching, I’d love to hear what experiences people have had with their distributions. Especially Nixos and Debian users, as those are what I’m considering myself.

How much configuration did it take to make the system usable? Are there some limitations with the repositories, distribution or OS in general? And importantly: have you learned something useful while working on your own system?

Did some distribution make you feel you were missing out on something important with your last distribution?

Have you had bad learning experiences with some distro? Have you switched away from distro for the same reason you installed it?

Would you suggest your distro for someone learning linux-admin skills? If you could go back, what distribution would you have used to 1) learning linux the first time 2) working in a jr-level position, still learning basic system administration, 3) when learning to code?

Thank you for your time and comments. I hope this post is general enough to be a worthwhile discussion.

  • chayleaf
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    1 year ago

    NixOS tends to encourage “proper” solutions instead of hacky temporary solutions, so while doing stuff on NixOS takes more time, maintaining what you’ve done is much easier, and it’s much easier to reason about, so I learned much more on NixOS than I learned on Arch (hell, I wrote two Nix DSLs for nftables and Lua because my perfectionism told me I need to do that instead of manipulating config as strings in Nix). I have an initrd hook that configures GPU passthrough by picking a GRUB option, I have a system configuration for an Arm router SoC (BPI-R3), which is a painful piece of hardware to work with, much like other SoCs, I have the router config itself (which I wrote a Nix framework for) - and if I ever forget how that all works, I can read the config to remember it, instead of trying to figure out what Linux commands I ran “back then”. But if your goal is just learning about Linux, look elsewhere - that was just a bonus for me; Nix is an abstraction, and you can only start learning Linux after you understand that abstraction.