I’m planning to install Arch Linux for the first time. Any recommendations on setup, must-have applications, or best practices? Also, what’s something you wish you knew before switching to Arch?
Do yourself a favour and install it on a virtual machine first. Screwing up an install on Arch is frighteningly easy. The Arch Wiki is your friend, use it. Also, read the installation instructions before you begin the installation, not during. If this sounds like too much of a headache (understandably so), then give EndeavourOS a whirl.
Only update your system if you have some time on your hands afterwards, in case something breaks. Happened to me a few times before.
So many tips, let me add mine.
- btop - for monitoring and process management
- pacseek - terminal UI for installing, searching packages (uses yay)
- chaotic aur - repo for prebuilt binaries that are generally ok
When installing use the archinstall the first time, unless you really want to go into the deep end and use the normal install.
- archinstall is one of the better/best distro installs around - it just does what it says it will and is pretty intuitive
- LUKS encryption is easy to set up in archinstall - strongly recommend encrypting your root partition if you have anything remotely sensitive on your system
- If you do use encryption but don’t like typing the unlock password every reboot, you can use tpm to unlock - yes, this is less secure than requiring the unlock password every time you reboot, but LUKS + TPM unlock is still MUCH better than an unencrypted drive just sitting there
- sbctl is a good tool for secure boot - If you want to get more secure, locking down bios with an admin password, turning on secure boot, sbctl works really well and is pretty easy to use. I would suggest reading up to understand what it’s doing before just installing/configuring/using it
- yay is a solid AUR helper / pacman wrapper
archinstall is still unstable as hell. I find that my best bet is to:
- Configure everything exactly like I want through the dialog
- Save the user and system preferences to their respective JSONs
- Mount a USB stick and copy the JSONs there
- Restart the archinstall process by loading from the JSONs, then hit commit
- When the above fails, restart the whole machine and jump to step 4, where it magically works
I didn’t read the documentation so I didn’t know you weren’t supposed to use sudo with yay.
-Ss can be added to pacman to search for packages. Pretty useful if you don’t want to DuckDuckGo them every time.
As for applications one neat one I don’t see recommended very often is xkill. You can use it to kill applications kind of like you would with the task manager in Windows. htop is probably a closer comparison to the task manager in general though.
There are a lot of Arch-based distros that are incredibly easy to install if you want a very easy setup process that doesn’t involve a lot of terminal work.
Start from the install guide on the wiki. It’ll branch out fast and just follow all the links and read. If something goes wrong, check if you missed something on the wiki. It’s an amazing resource.
Also, look up your hardware on the wiki before you start.
The ArchWiki is amazing, probably don’t start by installing nothing but a window manager and adding things you need as you go
Don’t?
Probably don’t start by installing nothing but a window manager
Oops. I ran into a lot of problems by doing this, but boy did I run into a lot of tools too
I have learned so much but everything is so disfunctional because “I’ll get to it later” means never
Use btrfs with snapshots. Verify you know how to boot into snapshot after a failed update and repair the system. This is the most important thing and lets you experiment much more freely.
I’ve been using Arch off and on for a long time, since it was horrible to install and updates did often break stuff. This is not the case now 🖖, and the Arch wiki is your friend.
-
Consider using btrfs with automated snapshots using yabsnap. It includes a configurable pacman hook in case something goes awry. Also just nice to have snapshots in case you accidentally delete a file or something.
-
Use paru, an AUR helper. Good for random things which may not be officially packaged. Expect to run into failures, and learn to diagnose them. Sometimes it’s just a new dependency the packager missed. For both paru and pacman, clean the cache once in a while or automatically, or things will get out of hand.
-
Do the “manual” setup, at least the first time, so you have an idea what’s going on. Don’t forget to install essential stuff like iwd (if needed) when you do pacstrap, or else you might have to boot from live again to fix it. Once you’re done, take care to follow the important post install steps, like setting up a user with sudo, a firewall, sshd, etc.
As for general setup, I’ve recently embraced systemd-networkd and systemd-resolved. Might be worth giving it a shot, since there is no default network manager like application. You can even convert all your wireguard client configs into networkd interfaces.
Best practice: Keep a personal log of various tweaks and things you’ve configured, and set up automated backups (more of general guidance).
Have fun!
-
EndeavorOS if you want to have an easy time. Also be comfortable reading documentation.
Why EndeavorOS over
arch-install
?Mostly BC its low effort. The most intimidating thing about arch for me was the troubleshooting when things go wrong. I’m cool with that in general operation but not during the installation process. Endeavor makes it painless while still being a minimalistic install
What issues were you having with arch-install that you had to troubleshoot?
Manually resizing/replacing the efi partitions for Windows dual boot was where I decided to stop and switch to a graphical installer.
Stick to the many guides available and you will be fine. One thing which I either missed or was glossed over in most guides is to install the Linux-firmware package. It is considered an “optional” package, but on all the machines I have ever used I have run into issues without it.
I wish I knew then that debbie does the trick for me
Install it in a VM. Create snapshots. When you fuck it up then revert the snapshot.
Once you’re decent at figuring out what to and not to do then try to get proficient at file system snapshots so you can do the same thing more or less on bare metal.
This, and take physical notes, or at least make notes in something you can refer to on a screen that is not your phone, ideally another desktop or a laptop computer with internet access in case something unexpected comes up during the physical install and you need to search the archwiki or the wider internet.
I wish I new how to easily install an AUR package manager when I first started.
Step 1: go to the AUR and choose a package manager. I recommend paru, but there are plenty of others.
Step 2: install git using pacman
sudo pacman -S git
Step 3: copy the git clone URL for paru and pull it
git clone https://aur.archlinux.org/paru.git
Step 4: CD into the new directory
cd paru
Step 5: install paru
makepkg -si
Now when you find a package from the AUR you want, you can easily install it.
paru -S [package]
Also, when you update your system, you only need to run
paru -Syu
. You don’t need to run bothpacman -Syu
andparu -Syu
.Great advice.
Btw you don’t need -S to install a package, just
paru packagename
Works fine
Why paru specifically?
Rust-based and actively developed
Rust based is not a feature it is a slogan. Yay is the defacto standard and also actively developed. That being said use whatever works for you and AUR.
Pacman is the only standard package manager for Arch. Arch recommends against using third party package managers, including Yay.
Also, just
paru
is equivalent toparu -Syu
Those who are (wisely) suggesting snapshots, do you guys use a different partitions for data and OS? Because if you do revert to an older snapshot after a while, you’d loose new data, too (unless you recover it from current state)?
archinstall’s default btrfs layout has I think 4-5 separate subvolumes (I’m not running btrfs anymore so can’t check) but at the very least I remember it has:
- /
- /var
- /home
being separate subvolumes and mountpoints, you can just use a previous snapshot from 1 without rolling back others
Related to the snapshotting stuff, timeshift-autosnap is pretty helpful, hooks into pacman and takes a snapshot before installing/updating packages.
Personally I found btrfs and the snapshots helpful when starting to use arch, but now that I know how not to blow things up, it has been stable enough for me I just felt ext4 was easier.
Cool.