This guide assumes that the reader is familiar with the GNU/Linux command line shell, and how to launch a graphical terminal if necessary. This install method can be done using any Parabola LiveISO. For a more user-friendly, mouse-centric install method, consider using the graphical installer on one of the LXDE LiveISO's desktop.
- 1 Download
- 2 Blind and visually impaired users
- 3 Creating the install media
- 4 Installation
- 4.1 Keyboard layout
- 4.2 Partition disks
- 4.3 Format the partitions
- 4.4 Mount the partitions
- 4.5 Connect to the Internet
- 4.6 Verification of package signatures
- 4.7 Install the base system
- 4.8 Install a kernel
- 4.9 Install a network manager
- 4.10 Other packages
- 4.11 Graphical Desktop Environments
- 4.12 Install a bootloader
- 4.13 Install wireless tools
- 5 Configure the system
- 5.1 Set host and hostname
- 5.2 Set timezone and locales
- 5.3 Generate initial RAM-disk
- 5.4 GRUB configuration
- 5.5 Configure speech support (for blind and visually impaired users)
- 5.6 Configure pacman
- 5.7 Service management
- 5.8 Setup users, groups, and passwords
- 5.9 Final steps
- 6 Update the system
- 7 Un-mount and reboot
- 8 Conclusion
- 9 Acknowledgement
- 10 See also
Download a Parabola GNU/Linux-libre ISO from the download page. These are provided with your choice of systemd or OpenRC as the default init system.
- The 'dual' ISOs can be booted into either an i686 or x86_64 live system. The 'net-install' ISOs will boot into a live system but will require an active connection to the internet for installation. The 'complete' ISOs will boot into a live system as well, but are capable of installing a full Parabola system with or without a connection to the internet.
- ISO images are signed and it is highly recommend to verify their signature before use. On Parabola GNU/Linux-libre, this can be done by using pacman-key -v <iso-file>.sig. On other systems: gpg --verify <iso-file>.sig. You may have to import the key from a keyserver with gpg --recv-keys <0x key ID>.
- The ISO image can be burned onto a CD, written onto a USB memory stick, booted directly by a virtual machine, or booted directly from GRUB. It is intended for new installations only or to be used as a recovery system; an existing Parabola GNU/Linux-libre system can always be updated with pacman -Syu.
- Checksums are provided for each edition in the accompanying SHA512SUMS and WHIRLPOOLSUMS files. They can be verified with: sha512sum -c SHA512SUMS and whirlpool-hash -c WHIRLPOOLSUMS.
2 Blind and visually impaired users
3 Creating the install media
3.1 Writing a Parabola ISO image to a CD/DVD
The Parabola Live ISOs can be burned to a CD or DVD most simply using a graphical tool such as 'brasero', 'k3b', or 'xfburn'. The 'cdrecord' utility can be used to burn a CD or DVD from the comand line.
3.2 Writing a Parabola ISO image to a USB drive
# dd if=[iso file] of=[usb device file] bs=1M && sync
[iso file] is the path to the ISO image file.
[usb device file] is the path to the USB device file. dmesg or lsblk --fs can be used to learn this path. It is often similar to device filenames of storage devices like hard drives and SSDs, e.g. /dev/sdb
4.1 Keyboard layout
For many countries and keyboard types appropriate keymaps are available already, and a command like loadkeys uk might do what you want. More available keymap files can be found in /usr/share/kbd/keymaps/ (you can omit the keymap path and file extension when using loadkeys).
4.1.1 Braille Support
TalkingParabola includes brltty, for those who own braille displays. The brltty package available on the TalkingParabola CD was compiled with as few dependencies as possible. If you wish to use braille, you will need to supply the brltty parameter at the boot prompt. Alternatively, you can start brltty from the shell, after the system has booted.
The brltty boot-time parameter consists of three comma-separated fields: driver, device, and table. The first is the driver for your display, the second is the name of the device file, and the third is a relative path to a translation table. You can use "auto" to specify that the driver should be automatically detected. You can read the brltty documentation for a fuller explanation of the program.
For example, suppose that you have a device connected to /dev/ttyS0, the first serial port. You wish to use the US English text table, and the driver should be automatically detected. Here is what you should type at the boot prompt:
Once brltty is running, you may wish to disable speech. You can do so via thekey, also known as . On my QWERTY keyboard, that key is located directly above the key, between and .
4.2 Partition disks
The choice of partitioning tools and layouts is a matter of preference, and beyond the scope of this install guide. See the partitioning guide for details and suggestions.
Remember to create any stacked block devices like LVM, LUKS, or RAID, if you choose to use those advanced partitioning technologies. You will also need to generate an initramfs and configure your bootloader properly to use it. Be aware that these all add complexity to your system, and therefore the potential for problems. Per the KISS principle, most people should not bother with them; but rather prefer a simple schema (eg: a MBR partition table, a single partition per OS).
4.3 Format the partitions
The choice of filesystems is a matter of preference, and beyond the scope of this install guide. See the filesystems guide for details and suggestions.
If you are using (U)EFI you will most probably need another partition to host the UEFI System partition. Read Create an UEFI System Partition in GNU/Linux.
4.4 Mount the partitions
Next, you must mount the target partitions. This guide uses /mnt as the mount-point of the root ('/') filesystem.
# mount /dev/<DEV_PART_2> /mnt # root ('/') filesystem (eg: /dev/mmcblk0p2)
You should also create directories as mount-points for, and mount onto them, any optional partitions which you created in the "Partition disks" and "Format the partitions" sections (eg: /mnt/boot, /mnt/home, ...). The /home and swap partitions are not essential in this step; but if you created them, and you want them to be auto-mounted when the new system boots, you should mount them now also. eg:
# mkdir /mnt/boot # mount /dev/<DEV_PART_1> /mnt/boot # boot ('/boot') filesystem (eg: /dev/mmcblk0p1) # mkdir /mnt/home # mount /dev/<DEV_PART_3> /mnt/home # boot ('/home') filesystem (eg: /dev/mmcblk0p3) # swapon /dev/<DEV_PART_4> # swap filesystem (eg: /dev/mmcblk0p4)
4.5 Connect to the Internet
A DHCP service is already enabled for all available devices. If you need to setup a static IP or use management tools such as Netcfg, you should stop this service first: systemctl stop dhcpcd.service. For more information read Network configuration.
Run wifi-menu to set up your wireless network. For details, see Wireless Setup and Netcfg. Note that this program is part of netctl, so OpenRC ISOs come with networkmanager instead. To perform the same task, simply run nmtui connect.
4.6 Verification of package signatures
Because packager's signing keys might have changed since the installation media was published, it is often necessary to update the keys before beginning an install.
# pacman -Sy archlinux-keyring archlinuxarm-keyring parabola-keyring # pacman -U https://www.parabola.nu/packages/core/i686/archlinux32-keyring-transition/download/
4.6.1 Errors during package verification
The most common error related to package signatures will be of the form:
error: some-package: signature from "A Packager <firstname.lastname@example.org>" is unknown trust :: File some-package.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] error: failed to commit transaction (invalid or corrupted package (PGP signature))
In most cases this can be corrected by refreshing that packager's key, or the entire the keyring. Note the email address shown in the error message (<email@example.com> in the example above). If only a smaller number of packagers are shown in the errors, copy the email addresses and run this command:
# pacman-key --refresh-keys firstname.lastname@example.org
Alternatively, you can refresh the entire keyring (it just takes a bit longer):
# pacman-key --refresh-keys
- If you face GPG errors during the install process, you may need to repeat these steps. If the first step fails, attempt to continue with the others.
- If you get an error related to dirmngr, you can get rid of it with:
# mkdir /root/.gnupg && chmod go-rx /root/.gnupg && touch /root/.gnupg/dirmngr_ldapservers.conf
(running the previous command might also be needed in the newly installed system.)
- It may be also possible that the system clock is behind and the keys are incorrectly marked invalid. To solve this, manually set the correct current time.
# date MMDDhhmm[[CC]YY][.ss]
- MM is the month
- DD is the day
- hh is the hour
- mm is the minutes
- CC is the century
- YY is the year
- .ss is the seconds (they can be omitted, but please remember to also remove the leading dot in that case)
For instance if the current time is 32 seconds and 44 minutes past 18 (6 pm) on the 13th November 2013 then the command would be:
# date 111318442013.32
4.7 Install the base system
Before installing, you may want to edit /etc/pacman.d/mirrorlist such that your preferred mirror is first. This copy of the mirrorlist will be installed on your new system by pacstrap as well, so it's worth getting it right.
If you face GPG errors when running # pacstrap, mind the advice in the signature verification section above. This is a fairly common error that you may see in the future as well; so it is a good idea to become familiar with the process of refreshing the keyrings.
This section describes the bare minimum requirements for every Parabola systemd system.
Install the Parabola systemd base system using pacstrap:
# pacstrap /mnt base
This section describes the bare minimum requirements for every Parabola OpenRC system. There are additional requirements that apply when installing a graphical desktop. Those are noted in a later section.
Install the Parabola OpenRC base system using pacstrap:
# pacstrap /mnt base libelogind udev-init-scripts
Beneath the OpenRC service manager, there needs to be a separate /sbin/init program, often called: the PID-1 provider. The OpenRC 'base' package group as installed above, contains openrc-init; which is fully adequate for most users. There are other compatible init programs however, that provide the openrc-pid1 pseudo-package if you have a preference. You can get an up-to-date list of providers by running expac -S '%n %P ' | sed -n '/ openrc-pid1[= ]/s/ .*//p'. Currently the options are:
- openrc-init (the OpenRC 'base' default): A minimal init program written specifically for OpenRC
- openrc-sysvinit: Use traditional Linux sysvinit as init
After installing an openrc-pid1 provider, OpenRC should boot by default instead of systemd. Note that it will boot to a command line, as the service for a graphical display manager has not yet been installed.
You also have a choice of udev implementations to set up hardware devices; but as with the init program, a fully adequate one ('eudev') is installed already with the OpenRC 'base' package group. You can get an up-to-date list of choices by running expac -S '%n %P ' | sed -n '/ udev[= ]/s/ .*//p'. Currently the options are:
- eudev (the base-openrc default): Gentoo's fork of udev
- systemd-udev: The traditional udev implementation
- notsystemd-udev: The traditional udev implementation, but compiled differently
4.8 Install a kernel
In order to have a fully bootable system, you will need to install a kernel. We recommend that you always have linux-libre-lts installed, even if you will normally use another. Additional kernels may be installed similarly.
# pacstrap /mnt linux-libre-lts
The linux-libre-lts kernel is the most stable and reliable kernel, and is fully adequate for most users. Unless you have particular reason to prefer another, this is an excellent choice for "everyday" use.
4.9 Install a network manager
In order to connect to the internet, you will need to configure your network devices. There are multiple ways to accomplish that; but the easiest is to install the NetworkManager service, which as the name suggests, will manage your network devices and connections automatically. This is an optional step, if you plan to manage your network using other tools.
# pacstrap /mnt networkmanager
4.10 Other packages
At this point, the system is very minimal - a great base for a customizing a special-case system, but not quite suitable for typical use. The 'parabola-base' meta-package contains several useful tools that were once standard, before the minimalist 'base' meta-package was introduced as the new standard base system. It includes the midnight-commander (mc) file manager, the vi and nano text editors, a man-page viewer, and support utilities for networking and file-systems, for examples.
# pacstrap /mnt parabola-base
If you have a btrfs root, you probably want to install also btrfs-progs. For f2fs, install f2fs-tools
4.11 Graphical Desktop Environments
Note that this section only describes the essential pre-requisites for graphical Parabola systems. The commands below will not install any X-server, display manager, window manager, or desktop environment. There are many possible combinations to choose from; but that is beyond the scope of this guide.
There are no special requirements during the initial install for using a graphical desktop with a Parabola systemd system.
This section describes the bare minimum requirements for using a graphical desktop with a Parabola OpenRC system.
The openrc-desktop package group installs essential software for graphical desktop environments.
elogind is a systemd substitute package. systemd is an essential 'base' package on Parabola systemd systems. Obviously, systemd is not an essential 'base' package on non-systemd Parabola systems; and is not installed by default. However, many GUI programs expect that systemd and it's dependencies are installed, and would have un-met dependencies if systemd or a substitute is not installed. There are multiple systemd substitutes; so you will need to choose one. elogind is the recommended option. It can grant privileges for desktop operations, such as powering off and mounting USB devices, and also provides systemd stub libraries, and depends on the same packages as 'systemd', in order to satisfy GUI programs which refuse to run otherwise.
# pacstrap /mnt openrc-desktop elogind
4.12 Install a bootloader
4.12.1 GRUB 2
- For BIOS and EFI:
# pacstrap /mnt grub
# pacstrap /mnt syslinux
4.13 Install wireless tools
If your wireless network is WPA protected, you'll need wpa_supplicant to connect to it:
# pacstrap /mnt wpa_supplicant
If you're using wifi-menu to connect, you'll also need the dialog package:
# pacstrap /mnt dialog
5 Configure the system
Generate an fstab with the following command (if you prefer to use UUIDs or labels, add the -U or -L option, respectively):
# genfstab -p /mnt >> /mnt/etc/fstab
Next we chroot into our newly installed system:
# arch-chroot /mnt
5.1 Set host and hostname
Add the following text to /etc/hosts, in the following form:
127.0.0.1 localhost ::1 localhost 127.0.1.1 MY_HOSTNAME.localdomain myhostname
If the system has a permanent IP address, the final ('MY_HOSTNAME') entry should refer to that, instead of 127.0.1.1.
Replace 'MY_HOSTNAME' with your preferred host name. Your computer's hostname can be anything that you like, consisting of letters a-z, digits 0-9, and hyphens '-' (eg: alices-laptop). The system hostname is mainly informational, making it easier to distinguish computers on your local network. This name will also appear in your shell prompt - eg:
On a systemd system, add the same chosen hostname to /etc/hostname, in the following form:
On an OpenRC system, add the same chosen hostname to /etc/conf.d/hostname, in the following form:
5.2 Set timezone and locales
- Symlink /etc/localtime to /usr/share/zoneinfo/Zone/SubZone. Replace Zone and Subzone to your liking. For example:
# ln -sf /usr/share/zoneinfo/Europe/Athens /etc/localtime
- Set locale preferences in /etc/locale.conf
- Add console keymap and font preferences in /etc/vconsole.conf when using systemd, or in /etc/conf.d/keymaps and /etc/conf.d/consolefont when using OpenRC.
- Uncomment the selected locale in /etc/locale.gen and generate it with locale-gen
5.3 Generate initial RAM-disk
- If you need special boot features, such as for disk encryption, configure /etc/mkinitcpio.conf accordingly (see mkinitcpio). In any case, re-generate the initial RAM-disk with:
# mkinitcpio -p KERNEL
... where: KERNEL is the one that you chose in the "Install a kernel" step (eg: linux-libre, linux-libre-lts). If you have installed multiple kernels, run the same command again for each kernel.
5.4 GRUB configuration
- To enable the GRUB bootloader at boot-time, install it to the boot disk, and generate an appropriate boot menu file: grub.cfg in the conventional location:
# grub-install /dev/sdX # grub-mkconfig -o /boot/grub/grub.cfg
... where '/dev/sdX' in most cases, is the same disk that you mounted in the pacstrap step, typically the only physical disk in the computer. Note: this is NOT the '/dev/sdXN' partition that you mounted on /mnt (e.g. /dev/sda1), but the physical raw disk root itself (e.g. /dev/sda).
5.5 Configure speech support (for blind and visually impaired users)
If you are using TalkingParabola and need start speech support when you boot the system, you will need to do:
- Install espeakup and alsa-utils.
- Save the state of the sound card, so that it will be retrieved on reboot:
# alsactl store
- Enable the espeakup systemd service by executing:
# systemctl enable espeakup.service
- Enable the espeakup systemd service by executing:
# rc-update add espeakup default
5.6 Configure pacman
Edit /etc/pacman.conf and configure pacman's options, also enabling the repositories you need.
If you are running systemd rather than OpenRC, make sure that the nonsystemd repo is NOT enabled.
If you are running OpenRC rather than systemd, make sure that the nonsystemd repo is enabled.
Also consider using Pacman2pacman, a peer to peer package system, in order to reduce load on official Parabola servers.
5.7 Service management
Most casual desktop users would rarely need to interact with the service manager; but it is a good idea to learn the basics. The process is the same, now while in the chroot, and afterward during normal use.
Interaction with systemd is done through the systemctl command. Read a:systemd#Basic systemctl usage for more information.
Systemd services normally must be manually "started" and/or "enabled" for auto-start. Interaction with OpenrRC is done through the rc-update, rc-service, and rc-status commands.
Newly installed services will need to be added to specific runlevels. The 'default' runlevel is the only one that most users will need. Note, however, that essential services are enabled by default (e.g. dbus, elogind, opensysusers and opentmpfiles). You will need to "chroot" into the target system first, in order to accomplish this. That will normally not be necessary, once the system is installed and running.
To activate the 'NetworkManager' service, for example:
# rc-update add NetworkManager default
5.8 Setup users, groups, and passwords
Set a root password with passwd:
Create an unprivileged (normal/everyday) user login (replace '<YOUR_USER_NAME>'):
# useradd -m <YOUR_USER_NAME> # passwd <YOUR_USER_NAME>
Add your user to any special groups, if needed. eg:
# gpasswd -a <YOUR_USER_NAME> wheel
See User management for advanced examples of users and groups.
There are no special requirements for users and groups with a Parabola/systemd system.
A Parabola/OpenRC desktop system requires unprivileged users to be in some extra permission groups. See the OpenRC article for details.
5.9 Final steps
Additional networking configuration may be needed for graphical wifi managers and other network management tools. See a:Network configuration and Wireless Setup; or ask for help on IRC, on the web forum, or on the mailing list, if you would like suggestions.
There are some subtle caveats to be aware of regarding OpenRC, in some system configurations, which have not been mentioned in this guide. The OpenRC article has some trouble-shooting advice for the most common problems. If you have a problem initially, with using your new OpenRC system, please read that article, first before reporting bugs.
6 Update the system
If you installed via the ARM Release Tarball, the RISC-V Release Tarball, or one of the "Complete" LiveISOs, you could upgrade the fresh system now. Otherwise, the fresh system is already up-to-date. Regardless, it is always safe to upgrade the system; and it is recommended to do so at least once per month.
Before upgrading the system for the first time, or anytime when a few months has past between upgrades, ensure that you have the current key-rings first:
# pacman -Sy archlinux-keyring archlinuxarm-keyring archlinux32-keyring parabola-keyring
Then upgrade the system:
# pacman -Syu
7 Un-mount and reboot
Exit the chroot, then un-mount any partitions which you mounted in the "Mount the partitions" step. Then you can reboot and login to the new system normally.
# exit # swapoff /dev/<DEV_PART_4> # if you mounted a swap partition (eg: /dev/mmcblk0p4) # umount /mnt/boot # if you mounted a separate /boot partition # umount /mnt/home # if you mounted a separate /home partition # umount /mnt # you surely mounted a / partition # reboot
Your new system is now fully functional Parabola GNU/Linux-Libre environment. Welcome to Fosstopia.