Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:manual:reference_installation [2022/04/05 18:38]
i3_relativism [Base system installation] add note regarding base-devel
en:manual:reference_installation [2024/03/26 23:21] (current)
throgh
Line 1: Line 1:
-<note warning> This page is still in progress, so please dont aprove this draft yet!</note> 
 ====== The Installation Guide ====== ====== The Installation Guide ======
-The intention of this reference Guide is to assist users in the process of installing **Hyperbola GNU/Linux-libre** from the live system booted with the official installation image. This page assumes you have some **level of experience** with GNU/Linux systems and utilities, especially with the command line. If you'd like a assited, step-by-step guide through the installation process, see the [[en:manual:beginner_installation|Beginners guide]]. Before beginning, we recommend you also check our [[en:project:faq|Frequently Asked Questions]], the [[https://wiki.archlinux.org/index.php/Frequently_asked_questions|Arch FAQ]], and employ the <color #620BB9/#EEDDFF>man ''command''</color> to read the man page of any command they are not familiar with. The Hyperbola wiki (known as **HyperWiki**), as well as the **ArchWiki**, should be the primary source of information and your first resource during trouble-shooting. +The intention of this reference Guide is to assist users in the process of installing **Hyperbola GNU/Linux-libre** from the live system booted with the official installation image. This page assumes you have some **level of experience** with GNU/Linux systems and utilities, especially with the command line. Before beginning, we recommend you to employ the <color #620BB9/#EEDDFF>man ''command''</color> to read the man page of any command they are not familiar with. The Hyperbola wiki (known as **HyperWiki**) should be the primary source of information and your first resource during trouble-shooting. 
  
-===== Braille Support ===== 
-There is a ISO called [[en:project:downloads#HyperTalking]] that is a derivative install image based on **TalkingArch** and a respin of the Hyperbola ISO modified to include speech and braille output. 
 ==== Blind and visually impaired users ==== ==== Blind and visually impaired users ====
-[[en:project:downloads#HyperTalking]] includes **brltty**, for those who own braille displays.  The [[https://www.hyperbola.info/packages/?q=brltty|brltty]] package available on the [[en:project:downloads#HyperTalking]] 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 <color #620BB9/#EEDDFF>brltty</color> from the shell, after the system has booted.+[[en:project:downloads#Hyperbola]] includes **brltty**, for those who own braille displays.  The [[https://www.hyperbola.info/packages/?q=brltty|brltty]] package available on the 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 <color #620BB9/#EEDDFF>brltty</color> 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 "<color #620BB9/#EEDDFF>auto</color>" to specify that the driver should be automatically detected.  I encourage you to read the <color #620BB9/#EEDDFF>brltty</color> documentation for a fuller explanation of the program. 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 "<color #620BB9/#EEDDFF>auto</color>" to specify that the driver should be automatically detected.  I encourage you to read the <color #620BB9/#EEDDFF>brltty</color> documentation for a fuller explanation of the program.
Line 43: Line 40:
  
 <code bash> <code bash>
-# dd if=~/hyperbola-milky-way-v0.2.1-dual.iso of=/dev/sr0 bs=2048 conv=noerror && sync+# dd if=~/hyperbola-milky-way-v0.4.3-dual.iso of=/dev/sr0 bs=2048 conv=noerror && sync
 </code> </code>
  
Line 50: Line 47:
  
 <code bash> <code bash>
-# dd if=hyperbola-milky-way-v0.2.1-dual.iso of=/dev/sdb bs=2048 && sync+# dd if=hyperbola-milky-way-v0.4.3-dual.iso of=/dev/sdb bs=2048 && sync
 </code> </code>
  
Line 96: Line 93:
 # rc-service dhcpcd stop # rc-service dhcpcd stop
 </code> </code>
- 
-For more information read [[https://wiki.archlinux.org/index.php/Network_configuration|Configuring Network]]. 
  
 The [[https://www.hyperbola.info/packages/?q=dhcpcd|dhcpcd]] network daemon starts automatically during boot and it will attempt to start a wired connection. Try to ping a server to see if a connection was established. For example, gnu.org: The [[https://www.hyperbola.info/packages/?q=dhcpcd|dhcpcd]] network daemon starts automatically during boot and it will attempt to start a wired connection. Try to ping a server to see if a connection was established. For example, gnu.org:
Line 209: Line 204:
  
 <note> <note>
-Currently, you may include a maximum of three nameserver lines. In order to overcome this limitation, you can use a locally caching nameserver like [[https://wiki.archlinux.org/index.php/Dnsmasq|Dnsmasq]].+Currently, you may include a maximum of three nameserver lines. In order to overcome this limitation, you can use a locally caching nameserver like **Dnsmasq**.
 </note> </note>
  
-You should now have a working network connection. If you do not, check the detailed [[https://wiki.archlinux.org/index.php/Network_Configuration|Network Configuration]] page.+You should now have a working network connection.
  
 === Wireless === === Wireless ===
Line 234: Line 229:
  
 <note> <note>
-If you do not see output similar to this, then your wireless driver has not been loaded. Please see [[https://wiki.parabola.nu/Wireless_Setup|Wireless Setup]] for more detailed information.+If you do not see output similar to this, then your wireless driver has not been loaded.
 </note> </note>
  
Line 250: Line 245:
 </code> </code>
  
-Then, your wireless chipset could need a <color #B90B0B/#FFDDDD>non-free firmware</color> to function. **This is not supported on Hyperbola**. Please see [[https://wiki.parabola.nu/Wireless_Setup|Wireless Setup]] if you are unsure if this is the true for your particular chipset.+Then, your wireless chipset could need a <color #B90B0B/#FFDDDD>non-free firmware</color> to function. **This is not supported on Hyperbola**.
 </note> </note>
  
Line 358: Line 353:
 === Behind a proxy server === === Behind a proxy server ===
  
-If you are behind a proxy server, you will need to export the <color #620BB9/#EEDDFF>http_proxy</color> and <color #620BB9/#EEDDFF>ftp_proxy</color> environment variables. See [[https://wiki.archlinux.org/index.php/Proxy_settings|Proxy settings]] for more information.+If you are behind a proxy server, you will need to export the <color #620BB9/#EEDDFF>http_proxy</color> and <color #620BB9/#EEDDFF>ftp_proxy</color> environment variables.
  
 ===== Installation ===== ===== Installation =====
 ==== Partition disks ==== ==== Partition disks ====
 +
 +<note important>
 +These instructions assume that you are using MBR (Master Boot Record) as the partitioning scheme for your installation disk. Installation on a GPT-based disk is slightly different than the process described here.
 +</note>
 +
 Once your computer has successfully booted into the Live USB device, type the following into you terminal: Once your computer has successfully booted into the Live USB device, type the following into you terminal:
  
Line 385: Line 385:
 Take note of the fact that the root partition that you soon will mount, is the bootable one (in this example the sda2) that you made from the rest of the space after creating the Swap partition. Take note of the fact that the root partition that you soon will mount, is the bootable one (in this example the sda2) that you made from the rest of the space after creating the Swap partition.
  
-See [[https://wiki.archlinux.org/index.php/Partitioning|partitioning]] for details. +Remember to create any stacked block devices like **LUKS**, or **RAID**.
- +
-Remember to create any stacked block devices like [[https://wiki.archlinux.org/index.php/LVM|LVM]], [[https://wiki.archlinux.org/index.php/Dm-crypt|LUKS]], or [[https://wiki.archlinux.org/index.php/RAID|RAID]].+
  
 ==== System Configuration ==== ==== System Configuration ====
Line 397: Line 395:
 <code bash> <code bash>
 # swapon /dev/sda1 # swapon /dev/sda1
-</code> 
- 
-=== Mount the root partition === 
-<code bash> 
-# mount /dev/sda2 /mnt 
 </code> </code>
  
Line 414: Line 407:
  
 ==== Format the partitions ==== ==== Format the partitions ====
-See [[https://wiki.archlinux.org/index.php/File_systems|File Systems]] for details. 
  
-If you are using (U)EFI you will most probably need another partition to host the UEFI System partition. Read [[https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface|Create an UEFI System Partition in GNU/Linux]].+If you are using (U)EFI you will most probably need another partition to host the UEFI System partition.
  
 === Create a file system === === Create a file system ===
Line 427: Line 419:
 === Mount the partitions === === Mount the partitions ===
  
-We now must mount the root partition on <color #0B71B9/#DDF1FF>/mnt</color>. You should also create directories for and mount any other partitions (<color #0B71B9/#DDF1FF>/mnt/boot</color>, <color #0B71B9/#DDF1FF>/mnt/home</color>, ...) and mount your [[https://wiki.archlinux.org/index.php/Swap|swap]] partition if you want them to be detected by <color #620BB9/#EEDDFF>genfstab</color>.+We now must mount the root partition on <color #0B71B9/#DDF1FF>/mnt</color>. You should also create directories for and mount any other partitions (<color #0B71B9/#DDF1FF>/mnt/boot</color>, <color #0B71B9/#DDF1FF>/mnt/home</color>, ...) and mount your swap-partition if you want them to be detected by <color #620BB9/#EEDDFF>genfstab</color>. 
 +=== Mount the root partition ===
  
-==== Verification of package signatures ==== +<code bash> 
-New packager keys are necessary by default to install **Hyperbola** from current ISOs. Because changes in existing keys might happen since rthe ISO release, it is recommended, if **not mandatory**, to update the keys before attempting an install.+# mount /dev/sda2 /mnt 
 +</code>
  
-<note important> +==== Verification of system-date ====
-Keep in mind these steps will fail if your system is not set to the correct time, or if you are not connected to the internet. See [[en:manual:reference_installation#connect_to_the_internet|above]] for internet setup instructions. +
-</note>+
  
 To check that your computer has the correct time, enter <color #620BB9/#EEDDFF>date</color> in the terminal. To check that your computer has the correct time, enter <color #620BB9/#EEDDFF>date</color> in the terminal.
Line 453: Line 445:
 # date 111318442013.32 # date 111318442013.32
 </code> </code>
- 
-Once the date is correct, we need to initialize the gnupg directory and update pacman's keys. 
- 
-<code bash> 
-# pacman-key --init 
-</code> 
- 
-<code bash> 
-# mount -o remount,size=100M,noatime /etc/pacman.d/gnupg 
-</code> 
- 
-<code bash> 
-# pacman-key --populate hyperbola 
-</code> 
- 
-<code bash> 
-# pacman-key --refresh-keys 
-</code> 
- 
-If you get GPG errors updating those packages, you can try running these commands to start over: 
- 
-<code bash> 
-# rm -r /etc/pacman.d/gnupg/* 
-</code> 
- 
-<code bash> 
-# pacman-key --init 
-</code> 
- 
-<code bash> 
-# pacman-key --populate hyperbola 
-</code> 
- 
-<code bash> 
-# pacman-key --refresh-keys 
-</code> 
- 
-If you get an error related to <color #620BB9/#EEDDFF>dirmngr</color>, you can get rid of it with: 
- 
-<code bash> 
-# mkdir /root/.gnupg && chmod go-rx /root/.gnupg && touch /root/.gnupg/dirmngr_ldapservers.conf 
-</code> 
- 
-For the time being, running the previous command might also be needed in the newly installed system. 
  
 ==== Base system installation ==== ==== Base system installation ====
Line 510: Line 458:
 You can install additional packages passing <color #620BB9/#EEDDFF>base</color> and the names of these packages as arguments after the root directory of the new installation (all packages from the **base group** are installed if no package is specified). You can install additional packages passing <color #620BB9/#EEDDFF>base</color> and the names of these packages as arguments after the root directory of the new installation (all packages from the **base group** are installed if no package is specified).
  
-<note> You can also use package group base-devel to include developement and contribution tools </note>+<note> You can also use package group **base-devel** to include developement and contribution tools </note>
  
 <note warning> <note warning>
 If you have a **btrfs root**, you probably want to install also [[https://www.hyperbola.info/packages/?q=btrfs-progs|btrfs-progs]]. If you have a **btrfs root**, you probably want to install also [[https://www.hyperbola.info/packages/?q=btrfs-progs|btrfs-progs]].
 </note> </note>
- 
-<note> 
-If you face GPG errors when running, you can try to fix them with: 
-<code bash> 
-# rm -r /etc/pacman.d/gnupg/* 
-</code> 
- 
-<code bash> 
-# pacman-key --init 
-</code> 
- 
-<code bash> 
-# pacman-key --populate hyperbola arch 
-</code> 
- 
-<code bash> 
-# pacman-key --refresh-keys 
-</code> 
-</note> 
- 
-==== Bootloader installation and configuration ==== 
-=== GRUB === 
-=== GRUB === 
-Finally follow these steps: 
- 
-<code bash> 
-# pacman -S grub 
-</code> 
- 
-<code bash> 
-# grub-install --target=i386-pc --recheck /dev/sda 
-</code> 
- 
-(Here do NOT append a partition number, i.e. <color #0B71B9/#DDF1FF>/dev/sdaX</color>) 
- 
-<code bash> 
-# grub-mkconfig -o /boot/grub/grub.cfg 
-</code> 
- 
-  * To configure the bootloader, you have to install it and generate the file <color #0B71B9/#DDF1FF>grub.cfg</color>: 
- 
-<code bash> 
-# grub-install /dev/sdX 
-</code> 
- 
-<note important> 
-If you want to [[en:manual:encrypted_installation|install GRUB on a Libreboot system]], keep in mind your system **does not use UEFI or Legacy BIOS**, but instead loads GRUB as its only payload. So you we will run this command instead: 
- 
-<code bash> 
-grub-install --no-bootsector /dev/sdX 
-</code> 
-</note> 
- 
-<code bash> 
-# grub-mkconfig -o /boot/grub/grub.cfg 
-</code> 
- 
-  * For BIOS and EFI: 
- 
-<code bash> 
-# pacstrap /mnt grub 
-</code> 
- 
-  * Install GRUB after chrooting (refer to the [[en:manual:reference_installation#Configure the system]] section). 
- 
-See [[https://wiki.parabola.nu/GRUB2|GRUB]] for further details. 
- 
-=== Syslinux === 
-<code bash>  
-# pacstrap /mnt syslinux 
-</code> 
- 
-See [[https://wiki.parabola.nu/Syslinux|Syslinux]] for further details. 
  
 ==== Wireless tools installation ==== ==== Wireless tools installation ====
Line 602: Line 477:
 </code> </code>
  
-Generate a [[https://wiki.archlinux.org/index.php/Fstab|fstab]] with the following command (if you prefer to use UUIDs or labels, add the <color #620BB9/#EEDDFF>-U</color> or <color #620BB9/#EEDDFF>-L</color> option, respectively):+Generate a **fstab** with the following command (if you prefer to use UUIDs or labels, add the <color #620BB9/#EEDDFF>-U</color> or <color #620BB9/#EEDDFF>-L</color> option, respectively):
  
 <code bash> <code bash>
Line 609: Line 484:
  
 === Chroot and configure the base system === === Chroot and configure the base system ===
-Next we [[https://wiki.archlinux.org/index.php/Change_Root|chroot]] into our newly installed system:+Next we need to enter directly our newly installed system:
  
 <code bash> <code bash>
 # arch-chroot /mnt # arch-chroot /mnt
 </code> </code>
- 
-  * Write your hostname to <color #0B71B9/#DDF1FF>/etc/hostname</color> 
  
 === Hostname === === Hostname ===
Line 638: Line 511:
 </code> </code>
  
-<code bash> 
-# echo myhostname > /etc/hostname 
-</code> 
  
-  * Symlink <color #0B71B9/#DDF1FF>/etc/localtime</color> to <color #0B71B9/#DDF1FF>/usr/share/zoneinfo/Zone/SubZone</color>. Replace <color #620BB9/#EEDDFF>Zone</color> and <color #620BB9/#EEDDFF>Subzone</color> to your liking. For example:+=== Locale ===
  
-<code bash> +Type the following to set locale preferences in <color #0B71B9/#DDF1FF>/etc/locale.conf</color>
-# ln -s /usr/share/zoneinfo/Europe/Athens /etc/localtime +
-</code> +
- +
-  * Set [[en:manual:beginner_installation#locale|locale]] preferences in <color #0B71B9/#DDF1FF>/etc/locale.conf</color> +
- +
-=== Locale === +
-Type:+
  
 <code bash> <code bash>
Line 658: Line 521:
  
 Now choose your locale from what language you’re using. All locales are commented out (preceded by #) by default. Uncomment (remove the #) for your choice of locale. For US English, it should look like this: Now choose your locale from what language you’re using. All locales are commented out (preceded by #) by default. Uncomment (remove the #) for your choice of locale. For US English, it should look like this:
- 
-<code bash> 
-# nano /etc/locale.gen 
-</code> 
  
 <code> <code>
Line 677: Line 536:
 </code> </code>
  
-Then create the <color #0B71B9/#DDF1FF>/etc/locale.conf</color>+Then check the file <color #0B71B9/#DDF1FF>/etc/locale.conf</color>. If not existing you can create it like following up:
  
 <code bash> <code bash>
Line 683: Line 542:
 </code> </code>
  
-Then export your chosen locale+Then export your chosen locale, just in case for your current session
  
 <code bash> <code bash>
Line 689: Line 548:
 </code> </code>
  
- +Add console keymap and font preferences in <color #0B71B9/#DDF1FF>/etc/conf.d/keymaps</color>
-  * Add console keymap and font preferences in <color #0B71B9/#DDF1FF>/etc/conf.d/keymaps</color>+
  
 === Keymap === === Keymap ===
Line 706: Line 564:
  
 <note>This only applies for CLI, is you are using X11, this won't affect your graphical environment.</note> <note>This only applies for CLI, is you are using X11, this won't affect your graphical environment.</note>
- 
-  * Uncomment the selected locale in <color #0B71B9/#DDF1FF>/etc/locale.gen</color> and generate it with <color #620BB9/#EEDDFF>locale-gen</color> 
  
 === Time zone === === Time zone ===
Line 742: Line 598:
 </code> </code>
 * Set a root password with <color #620BB9/#EEDDFF>passwd</color> * Set a root password with <color #620BB9/#EEDDFF>passwd</color>
-  * Add your user to the relevant [[https://wiki.archlinux.org/index.php/Users_and_groups|group]] such as:+  * Add your user to the relevant **group** such as:
  
 <code bash> <code bash>
Line 749: Line 605:
  
 ------------------------------ ------------------------------
 +==== Bootloader installation and configuration ====
 +=== GRUB ===
 +Finally follow these steps:
  
-  * Configure <color #0B71B9/#DDF1FF>/etc/mkinitcpio.conf</color> as needed (see [[https://wiki.archlinux.org/index.php/Mkinitcpio|mkinitcpio]]) and create an initial RAM disk with: 
-  
 <code bash> <code bash>
-mkinitcpio -p linux-libre-lts+pacman -S grub
 </code> </code>
  
-<note>linux-libre-lts is **our default kernel** since we are a long-term support distro.</note>+<code bash> 
 +# grub-install --target=i386-pc --recheck /dev/sdX 
 +</code>
  
-  * If you want to install GRUB for the (U)EFI modeyou will need to make sure that: +<note> 
-    * The computer booted in (U)EFI mode (if <color #0B71B9/#DDF1FF>/sys/firmware/efi</color> exist, then it booted in (U)EFI mode+Here do NOT append a partition numberi.e. <color #0B71B9/#DDF1FF>/dev/sdaX</color>
-    * The efivars module is loaded. (<color #620BB9/#EEDDFF>modprobe efivars</color> will load it)+</note>
  
---------------------------------+To configure the bootloader, you have to install it and generate the file <color #0B71B9/#DDF1FF>grub.cfg</color>:
  
-  * Configure the network again for newly installed environment. See [[https://wiki.archlinux.org/index.php/Network_Configuration|Network Configuration]] and [[https://wiki.parabola.nu/Wireless_Setup|Wireless Setup]].+<code bash> 
 +# grub-mkconfig -o /boot/grub/grub.cfg 
 +</code>
  
-<note tip> +=== Syslinux ===
-If you are following the [[en:manual:encrypted_installation|libreboot encrypted installation]] instructions, be sure to save a copy of grub.cfg on a thumbdrive in case the one flashed to libreboot is incorrect. You can use the grub shell to boot from the extra copy. +
-</note>+
  
-=== Configure speech support (for blind and visually impaired users) === +[[https://en.wikipedia.org/wiki/SYSLINUX|Syslinux]] is a collection of boot loaders capable of booting from drivesCDs, and over the network via PXE. Install the **[[https://www.hyperbola.info/packages/?q=syslinux|syslinux]]**-package with the following command:
-If you are using  [[en:project:downloads#HyperTalking]] and need start speech support when you boot the systemyou will need to do:+
  
-  * Install [[https://www.hyperbola.info/packages/?q=espeakup|espeakup]] and [[https://www.hyperbola.info/packages/?q=alsa-utils|alsa-utils]]. +<code bash>  
-  * Enable the espeakup service by executing: +pacstrap /mnt syslinux
- +
-<code bash> +
-rc-update add espeakup default+
 </code> </code>
  
-  * Save the state of the sound card, so that it will be retrieved on reboot:+For further details refer to the [[https://wiki.parabola.nu/Syslinux|corresponding article at Parabola]].
  
 +=== Create RAM-disk  ===
 +
 +Configure <color #0B71B9/#DDF1FF>/etc/mkinitcpio.conf</color> as needed (//see man-page for mkinitcpio//) and create an initial RAM disk with:
 + 
 <code bash> <code bash>
-alsactl store+mkinitcpio -p linux-libre-lts
 </code> </code>
 +
 +<note>linux-libre-lts is **our default kernel** since we are a long-term support distro.</note>
 +
 +If you want to install GRUB for the (U)EFI mode, you will need to make sure that:
 +    * The computer booted in (U)EFI mode (if <color #0B71B9/#DDF1FF>/sys/firmware/efi</color> exist, then it booted in (U)EFI mode)
 +    * The efivars module is loaded. (<color #620BB9/#EEDDFF>modprobe efivars</color> will load it)
  
 === Unmount and reboot === === Unmount and reboot ===
Line 814: Line 679:
  
 ===== Post-installation ===== ===== Post-installation =====
-You will now have to create a user and get user privileges like doas. And of course, you will have to install your favourite Desktop Environment (DE)+You will now have to create a user and get user privileges like doas. And of course, you will have to install your favourite desktop.
  
 === Configure pacman === === Configure pacman ===
 Edit <color #0B71B9/#DDF1FF>/etc/pacman.conf</color> and configure pacman's options, also enabling the repositories you need. Edit <color #0B71B9/#DDF1FF>/etc/pacman.conf</color> and configure pacman's options, also enabling the repositories you need.
- 
-See [[https://wiki.archlinux.org/index.php/Pacman|Pacman]] and [[en:project:repositories]] for details. 
  
 === Update the system === === Update the system ===
 At this point you should update your system. At this point you should update your system.
  
-See [[https://wiki.archlinux.org/index.php/Pacman#Upgrading packages|Upgrading packages]] for instructions.+<code bash> 
 +# pacman -Syu 
 +</code>
  
-=== Add an user === +=== Add an user and groups for privileges === 
-Finally, add a normal user as described in [[https://wiki.archlinux.org/index.php/Users and Groups#User management|User management]].+Finally, add a normal user.
  
 +<code bash>
 +# useradd -g users -m -s /bin/bash <username>
 +</code>
 +
 +You should consider the following groups to be used at start:
 +
 +<code bash>
 +# usermod -aG video <username>
 +</code>
 +
 +<code bash>
 +# usermod -aG audio <username>
 +</code>
 +
 +<code bash>
 +# usermod -aG sys <username>
 +</code>
 +
 +<code bash>
 +# usermod -aG storage <username>
 +</code>
 +
 +<code bash>
 +# usermod -aG optical <username>
 +</code>
 +
 +<code bash>
 +# usermod -aG power <username>
 +</code>
 +
 +<code bash>
 +# usermod -aG network <username>
 +</code>
 +
 +<code bash>
 +# usermod -aG input <username>
 +</code>
 +
 +If you want to access for updating:
 +
 +<code bash>
 +# usermod -aG wheel <username>
 +</code>
 +
 +Please remember also that to execute and access installed free, libre games you need another group-membership:
 +
 +<code bash>
 +# usermod -aG games <username>
 +</code>
 ==== Service management ==== ==== Service management ====
-Since Hyperbola [[https://www.hyperbola.info/news/end-of-systemd-support/|removed entire systemd support]], we suggest you read about [[https://wiki.gentoo.org/wiki/OpenRC|OpenRC]] which is our main default init system.+Since Hyperbola is oriented on init-freedom, we suggest you read about [[https://wiki.hyperbola.info/doku.php?id=en:system:init_systems:openrc|OpenRC]] which is our main default init system.
  
 ===== Conclusion ===== ===== Conclusion =====
Line 836: Line 750:
  
 ===== Acknowledgement ===== ===== Acknowledgement =====
-This wiki article is based on **ArchWiki**, **GentooWiki** and **[[https://wiki.parabola.nu/|ParabolaWiki]]**. We may have removed non-[[https://www.gnu.org/philosophy/free-system-distribution-guidelines.html|FSDG]] bits from it.+This wiki article is based on **[[https://wiki.parabola.nu/|ParabolaWiki]]**. We may have removed non-[[https://www.gnu.org/philosophy/free-system-distribution-guidelines.html|FSDG]] bits from it.