#Arch sudo user code#
Similarly, if you use VS code as your IDE, that too is “easy”.
For example, installing R is “easy”, and installing git is “easy”. Some of the set up tasks are easy, or at least as easy as anything gets on linux. Nevertheless, R is my first love so I always start there… Once upon a time that really meant getting R set up, but I’m a bit more polyglot nowadays (gasp!).
So um… yeah, future Danielle, best of luck!Īny time I get a new machine set up, my first discretionary task is to make sure that I can do data science work with it (that’s a depressingly revealing statement about me).
I have no idea whatsoever whether this had anything to do with me, or if the gods at large were messing with me or what. So I started trying to edit the nf settings and… actually I don’t think that fixed anything but weirdly after editing /etc/X11/nf the touchpad settings magically showed up in the GNOME settings panel and then I could edit them. Initially the settings panel in GNOME didn’t acknowledge that I even had a touchpad, which was annoying. I have a suspicion that it’s the noto-fonts package that does a lot of the work in fixing the issuesįixing the touchpad scroll direction and speed was awkward too. The best description on fonts I found was this gist. Arch doesn’t come with an extensive font library so the browser would often rely on fallback fonts for pages that don’t bundle the fonts, making a lot of pages look a bit unpleasant. Installing a decent browser ( firefox, obviously…) was easy, but not surprisingly the font situation for the web was a bit tricky. Instead I followed the instructions so I could start it with startx as soon as I log in, or choose to stay in the shell. I decided not to have the machine automatically boot into GNOME. I did, however, make one concession to nostalgia. I did think about other possible desktop environments besides old faithful, but in the end decided that I actually quite like the look and feel of default GNOME (even without the various tweaks that distros usually overlay on top of it) so I installed that. I added myself to the wheel group so that I can escalate to admin privileges using sudo, and I’m done.Īs much as the thought of returning to my childhood and running a computer without any desktop environment at all amused me… no. Anyway, the article walked me through the process so now I am danielle on my Arch box (insert the usual Australian joke about getting a root). It also highlighted things I’d never thought about with sudo before, mostly around which users have sudo privileges.
#Arch sudo user install#
Partly because it’s a nice walkthrough, but also because it clued me into the fact that Arch doesn’t come with sudo, so I had to install that. This article on adding users on Arch Linux was helpful. During the initial installation I set up a root user, but no regular users, so my first step was to give myself a … um, me. Setting up users was an odd exercise in reminding me that I’d forgotten what life was like before sudo. I thought I wouldn’t need to since I already had grub on my machine from the previous Ubuntu install but in the end it didn’t work without going through the GRUB install process Toward the end of the installation it tells you to install a bootloader. Eventually I got it to work when I installed NetworkManager and enabled rvice, which in turn only made sense to me after I’d read about start/enable and realised that “starting” a service sets it running in the background now, and “enabling” it means it will start automatically on startup. The network configuration step gave me some grief. It took me three tries to get a working installation, because I missed some subtle thing (e.g., the first time I didn’t have the bootable USB booting in UEFI mode, because obviously I would have thought of that at the beginning… sigh).Įverything became easier once I started feeling comfortable using pacman. The installation guide ( ) is good but dense, and I had to read a lot of the documents it links to in order to make progress. What I am going to do, however, is jot down my notes to myself on the process. My point is I have no business whatsoever in trying to guide anyone else through the installation process.
The only reason any of this happened is that I happened to have a spare laptop 2 and couldn’t think of anything better to do with it. Top of that list is that I am a complete amateur when it comes to Arch and I have no idea whatsoever what I’m doing. I have absolutely no intention of writing a “how to install Arch” guide, for many excellent reasons.
0 kommentar(er)
