HyperWiki

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 [2024/03/05 21:17]
gjason [System configuration] removed redundant mention of symlink localtime 		en:manual:reference_installation [2025/03/17 01:21] (current)
throgh [System configuration]
Line 3: Line 3:
  
 ==== Blind and visually impaired users ==== ==== Blind and visually impaired users ====
-[[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.+[[en:project:downloads#Hyperbola]] includes **brltty**, for those who own braille displays.  The [[https://www.hyperbola.info/packages/?q=brltty|brltty]] package available 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.  We encourage you to read the <color #620BB9/#EEDDFF>brltty</color> documentation for a fuller explanation of the program.
- +
-For example, suppose that you have a device connected to <color #0B71B9/#DDF1FF>/dev/ttyS0</color>, 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: +
- +
-<code bash> +
-arch32 brltty=auto,ttyS0,en_US +
-</code> +
- +
-Once <color #620BB9/#EEDDFF>brltty</color> is running, you may wish to disable speech.  You can do so via the "<color #620BB9/#EEDDFF>print screen</color>" key, also known as <color #620BB9/#EEDDFF>sysrq</color>.  On my qwerty keyboard, that key is located directly above the insert key, between F12 and scroll lock.+
  
 +Once <color #620BB9/#EEDDFF>brltty</color> is running, you may wish to disable speech.  You can do so via the "<color #620BB9/#EEDDFF>print screen</color>" key, also known as <color #620BB9/#EEDDFF>sysrq</color>.
 ===== Create bootable image ===== ===== Create bootable image =====
 ==== Download live image ==== ==== Download live image ====
Line 88: Line 81:
 <note warning>As of v197, **udev** no longer assigns network interface names according to the **wlanX** and **ethX** naming scheme. If you are coming from a different distribution or are reinstalling **Hyperbola** and not aware of the new interface naming style, please do not assume that your wireless interface is named <color #620BB9/#EEDDFF>wlan0</color>, or that your wired interface is named <color #620BB9/#EEDDFF>eth0</color>. You can use the command <color #620BB9/#EEDDFF>ip link</color> to discover the names of your interfaces.</note> <note warning>As of v197, **udev** no longer assigns network interface names according to the **wlanX** and **ethX** naming scheme. If you are coming from a different distribution or are reinstalling **Hyperbola** and not aware of the new interface naming style, please do not assume that your wireless interface is named <color #620BB9/#EEDDFF>wlan0</color>, or that your wired interface is named <color #620BB9/#EEDDFF>eth0</color>. You can use the command <color #620BB9/#EEDDFF>ip link</color> to discover the names of your interfaces.</note>
  
-A DHCP service is already enabled for **all available devices**. If you need to setup a static IP or use management tools, you should stop this service first: +A DHCP service is already enabled for **all available devices**. If you need to setup a static IP or use management tools, we will address this point later on.
- +
-<code bash> +
-# rc-service dhcpcd stop +
-</code>+
  
 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 121: Line 110:
 </code> </code>
  
-Identify the name of your Ethernet interface.+Identify the name of your ethernet interface.
  
 <code bash> <code bash>
Line 134: Line 123:
 </code> </code>
  
-In this example, the Ethernet interface is **enp2s0f0**. If you are unsure, your Ethernet interface is likely to start with the letter "**e**", and unlikely to be "**lo**" or start with the letter "**w**". You can also use <color #620BB9/#EEDDFF>iwconfig</color> and see which interfaces are not wireless:+In this example, the ethernet interface is **enp2s0f0**. If you are unsure, your ethernet interface is likely to start with the letter "**e**", and unlikely to be "**lo**" or start with the letter "**w**". You can also use <color #620BB9/#EEDDFF>iwconfig</color> and see which interfaces are not wireless:
  
 <code bash> <code bash>
Line 151: Line 140:
 </code> </code>
  
-In this example, neither **enp2s0f0** nor the **loopback** device have wireless extensions, meaning **enp2s0f0** is our Ethernet interface.+In this example, neither **enp2s0f0** nor the **loopback** device have wireless extensions, meaning **enp2s0f0** is our ethernet interface.
  
 You also need to **know these settings**: You also need to **know these settings**:
Line 161: Line 150:
   * Domain name (unless you are on a local LAN, in which case you can make it up).   * Domain name (unless you are on a local LAN, in which case you can make it up).
  
-Activate the connected Ethernet interface (e.g. **enp2s0f0**):+Activate the connected ethernet interface (e.g. **enp2s0f0**):
  
 <code bash> <code bash>
Line 284: Line 273:
 Follow this procedure if you need **ADSL with PPPoE/PPPoA** during the installation process. Follow this procedure if you need **ADSL with PPPoE/PPPoA** during the installation process.
  
-First, identify the name of your Ethernet interface.+First, identify the name of your ethernet interface.
  
 <code bash> <code bash>
Line 297: Line 286:
 </code> </code>
  
-In this example, the Ethernet interface is **enp2s0f0**.+In this example, the ethernet interface is **enp2s0f0**.
  
-Second, create the PPP net script and the net script for the Ethernet interface to be used by PPP:+Second, create the PPP net script and the net script for the ethernet interface to be used by PPP:
  
 <code bash> <code bash>
Line 489: Line 478:
 # arch-chroot /mnt # arch-chroot /mnt
 </code> </code>
- 
-  * Write your hostname to <color #0B71B9/#DDF1FF>/etc/hostname</color> 
  
 === Hostname === === Hostname ===
Line 511: Line 498:
 127.0.0.1                localhost.localdomain     localhost localhost 127.0.0.1                localhost.localdomain     localhost localhost
 ::1                             localhost.localdomain     localhost localhost ::1                             localhost.localdomain     localhost localhost
-</code> 
- 
-<code bash> 
-# echo myhostname > /etc/hostname 
 </code> </code>
  
Line 520: Line 503:
 === Locale === === Locale ===
  
-  * Set [[en:manual:beginner_installation#locale|locale]] preferences in <color #0B71B9/#DDF1FF>/etc/locale.conf</color> +Type the following to set locale preferences in <color #0B71B9/#DDF1FF>/etc/locale.conf</color>
- +
-Type:+
  
 <code bash> <code bash>
Line 529: Line 510:
  
 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 548: Line 525:
 </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 554: Line 531:
 </code> </code>
  
-Then export your chosen locale+Then export your chosen locale, just in case for your current session
  
 <code bash> <code bash>
Line 560: Line 537:
 </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 577: Line 553:
  
 <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 612: Line 586:
 # passwd # passwd
 </code> </code>
-* Set a root password with <color #620BB9/#EEDDFF>passwd</color> 
-  * Add your user to the relevant **group** such as: 
  
-<code bash> 
-# gpasswd -a <username> video 
-</code> 
- 
------------------------------- 
 ==== Bootloader installation and configuration ==== ==== Bootloader installation and configuration ====
 === GRUB === === GRUB ===
Line 636: Line 603:
 </note> </note>
  
-<code bash> +To configure the bootloader, you have to install it and generate the file <color #0B71B9/#DDF1FF>grub.cfg</color>:
-# 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> <code bash>
Line 646: Line 609:
 </code> </code>
  
-  * For BIOS and EFI:+=== Syslinux ===
  
-<code bash> +[[https://en.wikipedia.org/wiki/SYSLINUX|Syslinux]] is a collection of boot loaders capable of booting from drives, CDs, and over the network via PXE. Install the **[[https://www.hyperbola.info/packages/?q=syslinux|syslinux]]**-package with the following command:
-# pacstrap /mnt grub +
-</code>+
  
-  * Install GRUB after chrooting (refer to the [[en:manual:reference_installation#Configure the system]] section). 
- 
-=== Syslinux === 
 <code bash>  <code bash> 
 # pacstrap /mnt syslinux # pacstrap /mnt syslinux
 </code> </code>
  
-  * Configure <color #0B71B9/#DDF1FF>/etc/mkinitcpio.conf</color> as needed (see man-page for mkinitcpio) and create an initial RAM disk with:+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>
Line 667: Line 629:
 <note>linux-libre-lts is **our default kernel** since we are a long-term support distro.</note> <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:+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 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)     * The efivars module is loaded. (<color #620BB9/#EEDDFF>modprobe efivars</color> will load it)
- 
-=== Bootloader on external drive === 
- 
-  * Configure the network again for newly installed environment. 
  
 === Unmount and reboot === === Unmount and reboot ===
Line 703: Line 661:
  
 ===== 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.+You will now have to create a user and get user privileges like doas. And of course, you will have to install your additional environment for working.
  
 === Configure pacman === === Configure pacman ===
Line 767: Line 725:
 # usermod -aG games <username> # usermod -aG games <username>
 </code> </code>
 +
 ==== Service management ==== ==== Service management ====
 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. 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.
 +
 +==== Graphical environment and your favorite desktop ====
 +Hyperbola does not include the common known desktop-environments, for example Gnome, KDE, Xfce, Mate, Cinnamon, Budgie, LxDE or LxQT. If you want to know about our reasoning doing so, please read [[en:philosophy:incompatible_packages|here]] more about.
 +
 +You can for sure create your own working graphical environment as we offer several [[en:system:userspace:window_manager|window managers]] and [[en:system:userspace:desktop_enviroment:lumina_desktop|Lumina Desktop]] as working desktop-environment.
 +
 +==== Final note about included packages, applications and others ====
 +
 +We ask to make usage of the [[https://www.hyperbola.info/packages/|package-search]] so you can look out to find packages for your further installation, for example graphical file-managers and more. Hyperbola has not the goal to offer a wide number of packages as we focus on minimalism so far. So we do not have the interest to include more packages!
  
 ===== Conclusion ===== ===== Conclusion =====
-Your new **Hyperbola GNU/Linux-libre** base system is now a **functional GNU/Linux environment**.+Your new **Hyperbola GNU/Linux-libre** base system is now a **functional GNU/Linux-libre environment**. The rest is up to you for a decision which way your system should take.
  
 ===== Acknowledgement ===== ===== Acknowledgement =====
 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. 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.