• snekerpimp@lemmy.world
    18·
    7 months ago

    In all honesty, I use the arch manual to troubleshoot all distros. It is well written and has the info you need and no more.

  • Telodzrum@lemmy.world
    202·
    7 months ago

    I’ve found two things to be true after moving to Arch:

    1. The users on forums and other help boards are actually quite willing to link directly to the thing you should have read before starting a new thread and are generally polite about it.

    2. The Arch Wiki is really that good, so you should read it.

      • freijon@feddit.ch
        1·
        7 months ago

        Can’t say the same myself unfortunately. The community was one of the main reasons I moved to Gentoo. I’ve had so many bad encounters on the Arch IRC channel, they often made me feel like a complete idiot for not knowing certain things. On Gentoo on the other hand the community has very knowledgeable people but they don’t feel ‘elitist’ about it and are in fact very kind and helpful.

    • BassTurd@lemmy.world
      0·
      7 months ago

      I went straight from windows to Arch. I had used Ubuntu for a couple of weeks 10+ years ago. The arch wiki is a great resource and I was able to follow it to get up and running. However, there are things that aren’t detailed enough (like literally hold your hand) on some things the wiki expects you to know. Now, maybe starting with Arch is not the best path, so that’s probably mostly on me. I think that since there are so many different ways to do things, that following some of the instructions can be difficult for a user’s specific case. Boot loaders where my biggest hangup early on since I didn’t want to use Grub. Modifying boot loaders, setting up pacman hooks, learning and configuring different file systems, and learning how the config and system files is tough, and the wiki has all of the info to do it, but it’s not always linear. I wish there were more practical code examples and/or short videos showing exactly what files to modify and how to do it right.

      • Telodzrum@lemmy.world
        1·
        7 months ago

        That’s all fair. I think everyone should go through that process once and then use archinstall forever after that.

  • dunz@feddit.nu
    6·
    7 months ago

    I used to have a t-shirt that said RTFM, so useful as a linux tech😃. If someone asked something, I’d just point at the shirt jokingly and tell them where the documentation was

  • Delilah (She/Her)@lemmy.blahaj.zoneEnglish
    2·
    7 months ago

    You know liquid nitrogen cooling can get you some insane cinebench scores, but you can’t just pop a liquid nitrogen cooler in your PC and expect to boost your framerates. You need to disable so many safety things and if you don’t know why they were there in the first place you’re going to permanently damage your CPU.

    Archlinux is that but for software and because it’s software there’s no physical barrier to entry. Arch is powerful, but if you don’t know what you’re doing you’re better off with fedora or debian’s hand holding.

      • Delilah (She/Her)@lemmy.blahaj.zoneEnglish
        1·
        7 months ago
        • They come with apps like gnome software as standard, so you never interact with apt/rpm, flatpak or (barf) snap if you don’t want to. You might not even know which you’re installing.
        • They come with all sorts of configuration utilities like networkd (In my gentoo days I used wpa_supplicant directly and had no desktop integration with the wifi configuration. I was kinda stupid lol. Don’t use a distro to impress people kids), gui tools to manage your users and groups and something called “firewall configuration” which I don’t know the package for but is preinstalled on my fedora kinoite machine. (They are available in the arch repos, but unless you know what you’re looking for you wouldn’t think to install them.)
        • CUPS is preinstalled. If you don’t use an “unbloated to the point of madness” distro like arch or gentoo you’ve probably never heard of CUPS or interacted with it directly, but it’s the backbone of the linux (and macos) printing stack. In other words, printing should work out of the box wheras on arch that involves a trip to the arch wiki.
        • Integration packages are preinstalled. Things like the daemon that allows youtube videos in firefox tabs to be controlled by the play button on your keyboard if it has one.
        • Polkit is preinstalled, which allows applications to ask for sudo privileges and shows a popup box to the user asking their password. This is something you need to install manually on arch and gentoo, assuming you want that functionality and wouldn’t prefer to just only allow privilege escalation via sudo.
        • Most packages which ship with systemd services on debian (eg apache2, snapd, docker) enable that service by default. On arch this is usually not the case.
        • 3rd party debian and fedora repos ship binaries so once you’ve added them to your config they function identically to core packages. Most AUR packages have to be compiled from source either manually or through a helper like yay. (Note: there aren’t any helpers in the base system so you have to do at least one AUR build by hand before you get that part of the tech tree)
        • Even bash auto-completion is an extra package on arch. No really, open a terminal on debian and then type ls -- then double press tab. It should suggest valid arguments. This isn’t a thing on arch unless you install the bash-completion package
  • mihnt@lemmy.worldEnglish
    0·
    7 months ago

    Usually I’m not too phased by having to read something to learn, but damn if learning how to span video games over 3 monitors has been a daunting task for me.

    xrandr is something I’ve never been able to wrap my head around.

    • 0x4E4F@lemmy.dbzer0.comOP
      0·
      7 months ago

      BSD users are even worse than Linux users if you ask me… back in the day I mean, have no idea if things have changed the past 10 years or so.

      • pmk@lemmy.sdf.org
        1·
        7 months ago

        One thing I have learned using OpenBSD is actually reading the manpages first. After an install there’s a friendly mail from Theo, then afterboot(8) and intro(8) answers a lot of questions.