Fork me on GitHub

Build Yourself Arch Linux

Posted on November 21, 2016

Part 1: Base System

This is the first part of a series of articles on how I set up dual boot Arch Linux on my Mid 2014 MacBook Pro. At the end of this part I’ll have a bootable but completely minimal installation of Arch on an encrypted partition without any tuning. Ability to boot to Mac OS will be preserved.


December 11, 2016: clarify how to customize list of installed base package; add instructions how to start wired network automatically; describe a separate /data partition.

January 8, 2017: provide fix for startup hang caused by dhcpcd systemd service; add mkinitcpio hook for USB keyboard detection; use larger console font.

April 2, 2017: recommend overriding dhcpcd@.service systemd unit settings instead of editing the original file.


I had the idea of going back to using Linux for some time now. It’s hard for me to pinpoint a specific reasons for that. I’ve got feeling like I’m missing out lots of interesting stuff going on in the Linux world. Like the renaissance of containerisation and virtualization technologies, unikernels. While it’s true that almost all of that is made available for Mac, it oftentimes feels like terrible hacks has been done to make it work. Also, I’m inclined to think that I haven’t learned as much about computers as I could have during my time on OS X. I’m usually hesitant to learn proprietary things, well because of irrelevance of the knowledge outside of a cage. That way, I didn’t get to know OS X itself that well. I have learned the other side of “just works” - the feeling of helplessness when things do not work.

Latest Apple special event was just enough bullshit I can take. Do whatever you want with your TouchBar and feedbackless keyboard, Apple, but I’m leaving. But I’m not going to throw the computer I’ve spent about $3K on, so here I am, installing Arch Linux on my MacBook.

Given the above arguments one may ask why not just install Ubuntu for example. While Ubuntu is a good system to start with (I’ve used it myself for about two years) I wanted to try something different this time. The primary reason to try Arch Linux is learning. I have learned a lot when installing Arch Linux and writing this tutorial. The other thing is that I enjoy feeling of control over my machine. I like to know exactly what is installed and what is running on my computer, I don’t want to be distracted by the stuff I do not use. Also I like the idea of rolling release. To be able to run the latest version of packages and the kernel is nice.

While there’s no shortage of tutorials for installing Arch Linux on MacBook, everyone’s case is different, so my experience may be useful to someone. I’m not intend to write an exhaustive tutorial with every command one will need to execute, but rather an outline with links to already existing materials and how my personal setup differs. Please follow an awesome Installation guide and MacBook article on ArchWiki, think and read (or at least skim through) man pages of unfamiliar commands. I’m not liable for any damage caused by my writings to your computer so be careful. Let’s go.

Preparing the installation

Before start you’ll need to buy/borrow an Ethernet adapter for you Mac as WiFi probably won’t work out of the box. It is possible to install Arch Linux using WiFi but I decided to skip the hassle. See the wiki if you’re interested. Also, I would recommend to use an external display to no be blinded by your laptop’s brightness during the installation. I’m going to keep OS X on my laptop for foreseeable future and dual boot into Arch Linux. If you do not intend to do that some parts of the installation process will be simpler (at least you would not have to worry about wiping the wrong partition).

To keep OS X partition untouched I needed to shrink it to make some space for Linux. I split my 256G storage in half by shrinking the partition using OS X. There’re some hiccups: OS X El Capitan uses Core Storage Volumes by default and they are not easily resizeable. To resize the partition you’ll need convert it back to “native volume”. Before conversion volume needs to be unencrypted, you’ll have to turn FileVault off and wait a few ours until the disc will be decrypted. After that you can resize the OS X partition (using Disk Utils app or diskutil command) and turn FileVault back on.

First I had to grab an Arch Linux ISO which is around 800 MB. I always forget to verify downloads but it’s better to not skip this step. Read here how to verify the downloaded ISO using GPG. If you have no GPG installed, checksums are better than nothing. The GPG signature and the checksums are available on the download page. Preparing installation USB is dead simple, see the instructions. Reboot, hold Alt as soon as you hear startup sound and select your USB stick as a boot device. You’re in Arch Linux installation shell now.

Before proceeding I needed to configure the installation environment a little bit. Set font to something bigger (12x22) to be able actually see something (I use iso01-12x22). If you like me use something other than standard US layout, you’ll need to change the keymap. Because I use Workman layout I had to download a keymap for it from GitHub. If you want to remap Caps Lock to Control immediately, edit your preferred keymap file and set keycode 58 to Control as I did here for Workman. To download something from GitHub it is possible to use elinks browser from the shell. Adjust the system clock and lets continue onto the next step.

Disk partition

I want to have full disk encryption enabled for my Linux partitions. To do that I’ve decided to go with LVM on LUKS as one from available options. It means that there’s a single container encrypted using dm-crypt with LUKS and inside of the container there are multiple logical volumes managed by LVM. dm-crypt is the standard encryption functionality provided by the kernel itself and LUKS is a convenient utility to manage it. LVM is a flexible solution to manage logical partitions independently of the disk layout.

There’s a nice article on ArchWiki to help you decide what partition layout you want. I have settled on the following scheme: 20 GB for root partition; 12 GB for /var to prevent bewildered logs from eating up the space; 16 GB for swap partition; 18 GB for /home to store operational data and user configurations; as it is generally not recommended to share /home across OS installations I have created a separate /data partition for longer term storage (~47 GB).

First we would need a partition for our LVM container. Use fdisk -l (or any other partition tool) to take a look at what layout you’ve got already. In my case I’m interested in /dev/sda half of it occupied by OS X as /dev/sda1 and half of it free. I used gdisk to create a new partition of type 8E00 (Linux LVM). It was created as /dev/sda2. That’s pretty much all I need from gdisk, all the LVM volumes will be leaving inside of container /dev/sda2. NB: Apple recommends to have 200Mb gap between partitions for possible future use, use +200M as a start sector of your new partition, if you want to. We’re going to leave the existing UEFI boot partition as is so you would not need to create a new one for /boot.

If you want to be secure, the newly created container partition needs to be securely wiped first. Please, try to not mistype your empty partition number. Here is how to initialize encrypted LUKS container and slice it into partitions. Skip sections about the boot partition as we have it already. I’ve initialized LUKS with default encryption options as they seemed to roughly match what people recommend to use anyway. By this time you should have all the partitions mounted and formatted. Now mount your ESP to /mnt/boot.

Installing and configuring base system

First, check out if list of mirror servers looks sane. The highest priority servers were not from beyond an ocean and packages download speed was pretty high, so I’m fine with the defaults.

Now it’s time to markup the file system of your new OS and install the most necessary packages. If you want to be absolutely minimal and customize list of installed base packages, pass -i option to pacstrap and read here about syntax used. I do not need nano or mdadm (RAID management tool), for example. To keep my modified version of Workman layout, I copied the .kmap file to /mnt/usr/share/kbd/keymaps/. One more thing to do before you’ll switch into your brand new environment is to generate fstab.

Behold and enter the brave new world! Configure timekeeping, font, locale and keyboard, hostname. To figure out if your hardware clock is indeed set to UTC compare hwclock --utc and hwclock --localtime (unless you live in UTC :P). While wired network should work out of the box (I’m going to configure WiFi later), it won’t be started automatically. Set up root password, it will be possible to create non root users later.

I’m not a big fun of tiny fonts, so I installed terminus-font and used ter-132n (Terminus ISO8859-1 16x32 normal) for the persistent configuration. It looks much nicer and has much more comfortable to read size than the default 12x22 fonts.

To have network up after boot you’ll need to systemctl enable the DHCP service. It is recommended to enable DHCP for the specific interface. This is good to not turn on Wi-Fi automatically until requested and avoid possible conflicts with network management software. I ran into problems with this approach however: systemd was waiting for dhcpcd to be started for the wired interface for 90 seconds if the cable was unplugged. I found a solution on Arch Linux bug tracker. See the thread for the patch, you can override dhcpcd@.service template settings in /etc/systemd/system/dhcpcd@.service.d/override.conf (more details on overriding systemd units configuration can be found in man systemd.unit).


When computer is turned on the first thing that it runs is UEFI firmware. UEFI than launches an UEFI executable, systemd-boot boot manager that we will install later. systemd-boot is called “boot manager” and not “bootloader” because all it can do is to launch another UEFI applications from ESP. In our case it would be the Linux kernel. EFISTUB is a feature of newer kernels that allows it to act as an UEFI executable. Kernel than loads initramfs which is a set of prebuilt hooks to prepare the system to boot. After that actual OS boot starts from an init process, systemd in our case.

If root partition is encrypted so to be able to boot it needs to be decrypted first. To enable that initramfs hooks are required. To use custom console font and keyboard layout to enter encrypted partition password add consolefont and keymap hooks before encryption. I also experienced my DasKeyboard (connected via monitor USB hub) not being recognized sometimes at encryption password input stage. To avoid the problem add keyboard hook as well. After mkinitcpio, the tool used to build initramfs, is reconfigured, initramfs needs to be rebuild.


systemd-boot is a pretty simple boot manager to set up so I’ll use it to start. Later I’d like to try rEFInd and its beautiful themes. Installation of systemd-boot comes down to bootctl install. Here is how to configure it. This section on booting from encrypted partition is of particular interest. Notable you’ll need to add only Arch Linux entry by hands, OS X will be detected automatically at boot time based on the information available on ESP.

It is highly recommended to enable CPU microcode updates to ensure system stability. Don’t forget to update systemd-boot Arch Linux entry. You should be able to verify that you did everything properly by searching for “microcode updated” in system startup log using journalctl.

Now you’re ready to reboot into your new shiny OS. On startup you should be presented with systemd-boot menu. After selecting Arch Linux and before boot you’ll be presented with the prompt for your encryption password. After that you should see command line login prompt. Use root user for now.


While most of the things works as expected there’re few hiccups worth mentioning. First I’ve noticed that /var fails to be unmounted on shutdown. It looks like the problem is with the partition being busy because it’s used by systemd to write system shutdown logs. Quick search revealed that I’m not the only one having the problem unmounting separate /var partition and it should be forcibly unmounted by the end of shutdown process anyway. Still I’d like to make the unmounting error go.

Right now I have to type my password twice: once to unlock the encrypted partition and once to log in as a root user. To not have to do it twice I’m probably going to enable automatic login as a non-root user.

Be careful with doing anything while on battery as until suspend will be setup the machine will halt when run out of battery.

Closing thoughts

If you will find any problems I’ve failed to mention or any mistakes while following this guide please email me about them and I’ll update the post. I’ll appreciate any suggestions for improvements.

In some time I hope to post the second part of the guide. I’m going to focus on things like user and power management, wireless and continue to build the system upon the base I have.


To write this guide I relied heavily on ArchWiki, and three tutorials by Loïc Pefferkorn, Michael Chladek and Ron A.