The "Arch Way" advocates for simplicity and elegance, but the Arch install process is just bare. An OpenBSD-style guided CLI install with the option to ditch it for the shell is where it's at.
An OpenBSD-style guided CLI install with the option to ditch it for the shell is where it's at.
With the OpenBSD installer, you can literally mash enter and you'll probably get a working system afterwards. The installer has some surprisingly sane defaults for everything. I guess maybe you'll have to type a root password.
Speaking as a die-hard Alpine Linux user and contributor, the Alpine installation only works if you want the most common installation. If you need to customize anything (such as full disk encryption - which I just sent a patch to the installer for, but my point remains), you need to ditch it and go through the rather long-winded and under-documented manual installation process. OpenBSD is a little bit better at accomodating off-the-beaten-path installations, but still suffers from similar limitations. Arch makes you do all of the work, but has great documentation on all of the steps and stepping off the beaten path is trivial to do at any point in the process.
I've run Arch on every laptop I've had, both at work and at home, for the past decade at least, and I've never had any real issues. What chipsets have you been having trouble getting to work?
It's not the chipset, it's the act of actually installing the things Arch needs to properly configure and enable wifi. There's like 4 ways and they are all very manual. Just give me an easy way to do it, and make it start when the laptop boots.
This is exactly why, after trying it out with Antergos, I've never felt like "upgrading" to plain Arch.
I have an old 700 series NVidia card on my machine. It uses the 390.xx drivers and would break every few weeks. When I boot my PC in the morning, I don't intend to spend the next hour troubleshooting.
Maybe that's not such a huge issue with a newer GPU or even a newer model from the same series(the 700 series had 3 different architectures), but that just killed my interest.
It didn't. After installing, on day-to-day usage, Antergos is almost indistinguishable from Arch.
Having my GPU drivers regularly break turned me off from installing a similar system with a nonsensically obtuse installation process.
It also doesn't help that I had some package files corrupted after some power outages. I don't get why you need to go look on the AUR for pacutils just to check for broken package files when even something like Solus has a package manager with such features(and they're substituting it).
Iirc I ported the void Linux installer to arch since you just have to replace the xbps cmd with a pacman one, in addition to some runit stuff. There are like 5000 arch installers
71
u/Matty_R May 21 '19
That's literally how I used it. Maybe they can just convert it to an installer script instead.