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:30]
throgh [Blind and visually impaired users] 		en:manual:reference_installation [2025/03/17 01:21] (current)
throgh [System configuration]
Line 81: 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 114: Line 110:
 </code> </code>
  
-Identify the name of your Ethernet interface.+Identify the name of your ethernet interface.
  
 <code bash> <code bash>
Line 127: 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 144: 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 154: 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 277: 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 290: 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 589: Line 585:
 <code bash> <code bash>
 # passwd # passwd
-</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> </code>
  
------------------------------- 
 ==== Bootloader installation and configuration ==== ==== Bootloader installation and configuration ====
 === GRUB === === GRUB ===