And technically the key file can just be a plain text password and still work. Just as long as the key file matches the drive’s encryption password.
And technically the key file can just be a plain text password and still work. Just as long as the key file matches the drive’s encryption password.
If its encrypted, you can also decrypt the drive automatically once booted by adding an entry in /etc/crypttab
This will make it so you don’t have to type the password.
Per the Arch Wiki:
The AUR is unsupported, so any packages you install are your responsibility to update, not pacman’s. If packages in the official repositories are updated, you will need to rebuild any AUR packages that depend on those libraries.
They have a whole wiki for the AUR.
To update the package, you use git to pull the latest branch code and repeat the process. You should double check if there are dependency changes though.
Like I said, its easier with a pacman wrapper, but not necessary.
You definitely do not need to use any pacman wrappers to build a package from the AUR. Those tools make it easy, yes, but are not required.
Building a package can be as simple as
git clone AURpackagehere
cd AURpackagehere
makepkg -si
They acknowledge many wrappers, not just yay. However, none are officially supported.
Pacman is the only standard package manager for Arch. Arch recommends against using third party package managers, including Yay.
What issues were you having with arch-install that you had to troubleshoot?
Rust-based and actively developed
Why EndeavorOS over arch-install
?
Do not allow http or ftp traffic as this guide suggests, unless you are active as a server for your local network on those particular ports, and you are behind a NAT firewall that your router usually provides.
I love that Mint brings people to Linux, but its users write some silly guides sometimes.
deleted by creator