I notice myself asking questions about common tasks when I come back to Arch after a long time. I think that makes for a good article as it is possible others have these questions. I’m running out of space and that’s stupid. Not a question, but I’ve felt that exact sentiment. In Arch, this is very likely the Pacman cache going crazy. Everytime you upgrade a package in Pacman, it keeps the previous version.
I have trouble sometimes navigating network connectivity using Arch. The OS doesn’t really have an issue getting out to networks, I just seem to not remember what to do in a time of need. Unfortunately, it is usually the first thing you need to do to begin the problem solving process. It is not lost on me that I am posting this article on the Internet. You’ll find it after you get in to trouble.
This seems to be a bit of a nightmare with Arch. I think the issue is that it is difficult to test. I typically connect to pretty good networks that have passwords and reasonable security. On vacation though, I don’t have a choice of what to connect to. I really don’t know what the advantage of WPA Enterprise is with the stupid login page. There is no way that is more secure.
Before going on, make sure you meet the requirements: General recommendations after an Arch install can be found here. I’m going to use this article to collect my list of requirements. Okay, you have to install sudo. You also need a user. And a sudo group. use visudo to edit the sudoers file. groupadd sudo will add the sudo group. then you can gpasswd -a drone sudo to add drone to the sudo group.
I wanted to install Arch because all the cool kids do it. Really, what I wanted was more control over the system and the decisions I had to make to get it to work. In the past, I have favored speed of installation and stability of the installation because I didn’t want to spend time configuring stuff that didn’t relate to what I wanted to accomplish. That basically means LTS Ubuntu.