Arch Linux – Best Tips for Beginners?

[corrodedcranium@leminal.space]

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

[treadful@lemmy.zip]

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.

[corrodedcranium@leminal.space]

And the neofetch print out

[corrodedcranium@leminal.space]

Why paru specifically?

[corrodedcranium@leminal.space]

It doesn’t hurt to have the LTS kernel installed as a backup option (assuming you use the standard kernel as your chosen default) in case you update to a newer kernel version and a driver here or there breaks.

I had a similar issue that was resolved by swapping to the LTS kernel. Learning about using a bootable Arch USB and chrooting into your install to make repairs would be a good thing for OP to know

[pumpkinescobar@lemmy.world]

• 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

[abrasiveteapot@sh.itjust.works]

Great advice.

Btw you don't need -S to install a package, just

paru packagename

Works fine

[9tr6gyp3@lemmy.world]

Why EndeavorOS over arch-install?

[9tr6gyp3@lemmy.world]

Rust-based and actively developed

[tetris11@lemmy.ml]

archinstall is still unstable as hell. I find that my best bet is to:

1. Configure everything exactly like I want through the dialog
2. Save the user and system preferences to their respective JSONs
3. Mount a USB stick and copy the JSONs there
4. Restart the archinstall process by loading from the JSONs, then hit commit
5. When the above fails, restart the whole machine and jump to step 4, where it magically works

[chaoticnumber@lemmy.dbzer0.com]

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.

[ndondo@lemmy.dbzer0.com]

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

[loo@lemmy.world]

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

[9tr6gyp3@lemmy.world]

What issues were you having with arch-install that you had to troubleshoot?

[azron@lemmy.ml]

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.

[twirl7303@lemmy.world]

Manually resizing/replacing the efi partitions for Windows dual boot was where I decided to stop and switch to a graphical installer.

[onlooker@lemmy.ml]

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.

[9tr6gyp3@lemmy.world]

Pacman is the only standard package manager for Arch. Arch recommends against using third party package managers, including Yay.

[downhomechunk@midwest.social]

Install slackware instead! But if you must, yay.

[dima@feddit.uk]

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