I’m a little bit underwhelmed, I thought that based off the fact so many people seem to make using this distro their personality I expected… well, more I guess?

Once the basic stuff is set-up, like wifi, a few basic packages, a desktop environment/window manager, and a bit of desktop environment and terminal customisation, then that’s it. Nothing special, just a Linux distribution with less default programs and occasionally having to look up how to install a hardware driver or something if you need to use bluetooth for the first time or something like that.

Am I missing something? How can I make using Arch Linux my personality when once it’s set up it’s just like any other computer?

What exactly is it that people obsess over? The desktop environment and terminal customisation? Setting up NetworkManager with nmcli? Using Vim to edit a .conf file?

  • matcha_addictEnglish
    2·
    4 months ago

    Bunch of random small things gave me issues. Sdkman (kinda like a Java version manager) and transmission on arm64 on wireguard would not work either.

    • PureTryOut@lemmy.kde.social
      1·
      4 months ago

      I ran transmission and WireGuard for ages before I recently switched my server over to x86, worked fine?

      Idk about Sdkman though, I don’t do Java development, but if it’s written in Java itself I fail to understand why it wouldn’t work 🤔

      • matcha_addictEnglish
        1·
        4 months ago

        My setup was really weird. I was running it under a network namespace. Maybe that’s why? The app would run like normal, but it would not successfully create any connections. I replicated the same setup on glibc and it worked.