Arch Linux

Introduction

Arch is a very DIY OS.  Even though it is less so than Gentoo or Linux From Scratch,  there is the expectation that you know enough about system-level things to do the installation.  They also have lots of options, so it's even more important to know enough to make decisions on those options.  

If you want to be such a techie and/or want to learn your way around the Linux operating system, Arch is a good place to start.  If you aren't a techie at all, it is possible, just expect to really roll up those sleaves!

All that said, I have an Arch system, though I don't regularly use it.  😉  Once you get used to it all, it is pretty easy to maintain.  And, yes, you can brag if you've keep it all up and running.

Installation

Okay, want to do the brain-dead thing and get to bragging without learning?  Instead of starting with Arch's installation guide, you can use the steps below that I've "compiled".  I keep it so I don't have to jump around the pages on Arch's wiki to relearn their style of Linux implementation.  In order to use it, you will need some experience with Linux, or willingness to search.  Also, as of 1/1/2025, the steps work; at least that is when I reloaded my Arch computer from scratch.

I use fdisk and usually create a new GPT or MBR.

AUR

The Arch User Repository has lots of packages outside the core supported packages.  They are community created & maintained, so understand what that means.  In general, it is a multi-step process.  You have to find the package here, clone the PKGBUILD using GIT, build it, and finally install it.  

Because it is community driven, always do your research.  After getting the build files, check to make sure everything looks cool.  Some effort is better than no effort and not catching everything is not an excuse, to me, to not do anything at all.  

I also like to do this manually, not via a GUI.  How often do you install packages?  So I create a directory /home/System/aurbuilds/ and do all the work there.  For packages & packagers I know I use these commands:

The last command means you will have to (re)build everything again if you want to reinstall.  It deletes all files not tracked by git.  Using the -r option in makepkg might better suit your needs.  I personally like cleaning up the disc space and starting from scratch when I run into issues.

I do this for Google Chrome and Github Desktop.