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/06/17 01:15]
throgh [Conclusion] 		en:manual:reference_installation [2024/07/18 03:27] (current)
throgh [Connect to the Internet]
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>