• bob_wiley@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Right, the live environment was easy. The drivers were there, the utility was there. Pull the list of networks, put in the password, good to go. I know half the point of Arch is doing it yourself, but if it auto-detects your network card, and it knows you’re on wifi… maybe install that stuff so things keep working instead of acting like it’s 2002 and most people are on a wired connection. Arch without a network connection is basically useless. I don’t think most users know what driver their wifi card needs, so it’s just a matter of installing a bunch of shit until something works, which makes the install feel a whole lot less clean. I get wanting to pick and choose packages, but if it can auto-detect and support the basic hardware, that seems like like it would be the minimum viable OS.

    And I don’t know if things changed. I probably did this around 2014 or 2015, so it’s been a while.

      • bob_wiley@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Yeah, it does help the user know their system, which is a good thing for if/when there are issue down the road. Although I think if I was really after the learning experience I’d probably go with Linux from Scratch or Gentoo.

        I hadn’t heard of archinstall before. I’m not a big fan of the warnings, it’s seems like they’re telling people they really shouldn’t use it, lol.

        https://wiki.archlinux.org/title/Archinstall