Arch Linux – Best Tips for Beginners?
-
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
-
Only update your system if you have some time on your hands afterwards, in case something breaks. Happened to me a few times before.
-
What issues were you having with arch-install that you had to troubleshoot?
-
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.
-
Manually resizing/replacing the efi partitions for Windows dual boot was where I decided to stop and switch to a graphical installer.
-
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.
-
Pacman is the only standard package manager for Arch. Arch recommends against using third party package managers, including Yay.
-
Install slackware instead! But if you must, yay.
-
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
-
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 undersided result is going "hmm what do these all do, why do I have 2000+ packages"
-
-
-
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.
-
Are you talking about archinstall or have they actually automated the default installation method?
-
-
i thought yay told you to not run it with sudo?
-
Ah, good to know. I haven't really used that save configuration and reuse process, I just do the install directly at the end of configuring everything. But I can see the draw for using that, a shame it doesn't seem to work that well.
-
-
It does. It gives you this message
-> Avoid running yay as root/sudo.
I only ran Debian and Ubuntu based distros up until that point so I thought you always needed to install packages using sudo.
I am pretty sure I ignored the warning initially because the first couple packages I tried to install with sudo and yay worked.
This was a while ago.
-
Any reason you would recommend Slackware specifically?
I've watched a few Youtube videos on the history of it and the advantages of it but I don't recall much. It seemed like a lot of people who had used Slackware a long time ago simply continuing to use Slackware and people using at as a learning tool because of how user involved it is.
Would you recommend people start with Slackware itself or a Slackware-based distro?
