Linux

don't use archinstall if it's the first time, the manual installation is not that hard

Be aware that some apps will install fine from the arch repo but some others will be better installed from flatpack (e.g. inkscape) or directly as an executable (e.g. Godot).

On steam you may need to specify your video card if you run an AMD card using the DRI prime command. Some games will require -vulkan to use vulkan rather than game settings.

Don't cheap out and use the hand holding script to ez mode the install. At least not the first time. You will learn a few things along the way.

Use EndeavousOS instead because the initial install process is simpler.

Check ArchLinux.org for news before you kick off an update. It's got an RSS feed and a mailing list if that helps.

Read the Wiki, and turn to it first for any issues you have.

This one may be a special "me" problem, but if you're manually interacting with wpa_supplicant, stop and go read the Networking page in the Wiki again.

Learn how to use journalctl (at least superficially) before something goes wrong.

Generally you want to restart after an update to the kernel or graphics drivers or things start degrading strangely.

From the bottom of the installation guide: https://wiki.archlinux.org/title/General_recommendations

• EndeavourOS is arch based with less hassle. Its more than good enough for most people. don't get trapped by minimal install bs and other non-consequential opinionative approaches to software.
• Select btrfs as your file system and use timeshift. If you fuck up or if your updates fuck something up. There are other ways of doing rollbacks and this is just what I became familiar with. I've used it two times in the past year, its worth it.
• Bookmark the archwiki, 99% of the time the answer to the questions of 'how to' and 'can i' are in there
• There are multiple DE's. Pick what works best for you before you toss that bootable USB installer. You of course can switch later down the line, but experimenting now will save you config troubleshooting later, just stick to what feels/looks best. Look around on the web to see what appeals to your workflow. There are others like Cosmic and Wayland that are not included in the arch gui installer, in which case, follow the install procedures for the DE you want and remove the old ones to avoid config overlap.
• Have Fun. If you are not, do something that is.

The whole arch advantage (imo) is that you have a full understanding of what's in your machine and how it works.

As a beginner you won't understand and that's okay, but you should try different things (or don't and just focus on what works for you) as long as the end result is you doing: pacman -Qe and going "hmm that makes sense", and imo the undesired result is going "hmm what do these all do, why do I have 2000+ packages"

For starts, read the wiki. Specifically, read the installation guide at least twice to get a feel for how it works and what the Arch vibe is like. This is also your chance to figure out just what you want to do. Do you want to use GRUB or UEFI? Which sounds like a better fit? What filesystem? What do you want to run? mdadm or not? A little bit of planning and reading is better than reinstalling half a dozen times (ask me how I know...)

Must-have applications? Screen or tmux. SSH. Whatever shell you're comfortable with (bash is how I roll, but you might be a fan of fish).

Only update your system if you have some time on your hands afterwards, in case something breaks. Happened to me a few times before.

Arch is good for tinkering with to make it your own, but can sometimes require tinkering to do things other distros can do straight away, e.g. adding udev rules to use certain devices or setting up zeroconf to be able to discover printers on the network automatically

If you want to be able to roll back changes easily you could set up your root and home partitions as btrfs subvolumes and use snapper to take snapshots, which can be combined with pacman hooks to automatically take snapshots when updating/installing software and can even be set up to allow booting into the snapshots which could be useful if you break your system

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.

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.

The ArchWiki is amazing, probably don’t start by installing nothing but a window manager and adding things you need as you go

Print out the install guide on paper and have it with you while you go. If you fuck up networking, you'll have the directions there to get it back.

• 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

EndeavorOS if you want to have an easy time. Also be comfortable reading documentation.

Install slackware instead! But if you must, yay.

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.

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'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.

1. 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.

2. 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.

3. 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!