User Tools

Site Tools


secure_ubuntu_system:initial_setup

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
secure_ubuntu_system:initial_setup [2020/05/20 21:38] petersecure_ubuntu_system:initial_setup [2022/07/19 10:21] (current) – [Configure the network] 85.203.36.242
Line 1: Line 1:
 ====== Secure Ubuntu System - First Configuration ====== ====== Secure Ubuntu System - First Configuration ======
 +
 +{{:secure_ubuntu_system:first_config.png?100|}}
  
 ===== Login ===== ===== Login =====
Line 5: Line 7:
 Login to the newly installed system with your previously created Administrator's username and password (e.g. <color red>administrator</color> and <color red>adminpass</color>). Login to the newly installed system with your previously created Administrator's username and password (e.g. <color red>administrator</color> and <color red>adminpass</color>).
  
 +----
  
 ===== Get root privileges (Optional) ===== ===== Get root privileges (Optional) =====
Line 57: Line 60:
 </code> </code>
  
-This is done for safety.  If the file becomes messed up the original can be restored.+<WRAP info> 
 +**NOTE:**  This is done for safety.  If the file becomes messed up the original can be restored. 
 +</WRAP> 
  
 ---- ----
Line 130: Line 136:
 Instead you need to specify your nameservers in your network configuration.  Use the command **man resolveconf** to find out more. Instead you need to specify your nameservers in your network configuration.  Use the command **man resolveconf** to find out more.
  
-  * Traditionally, the file /etc/resolv.conf was a static configuration file that rarely needed to be changed or automatically changed via DCHP client hooks.+  * Traditionally, the file **/etc/resolv.conf** was a static configuration file that rarely needed to be changed or automatically changed via DCHP client hooks.
   * Nowadays, a computer can switch from one network to another quite often and the resolvconf framework is now being used to track these changes and update the resolver's configuration automatically.   * Nowadays, a computer can switch from one network to another quite often and the resolvconf framework is now being used to track these changes and update the resolver's configuration automatically.
   * It acts as an intermediary between programs that supply nameserver information and applications that need nameserver information.   * It acts as an intermediary between programs that supply nameserver information and applications that need nameserver information.
Line 283: Line 289:
 eth1: no autonegotiation, 1000baseT-FD flow-control, link ok eth1: no autonegotiation, 1000baseT-FD flow-control, link ok
 </code> </code>
- 
-Ensure that all interfaces are shown.  If not, then revisit the above config changes around the network. 
  
 In the example output above, we can see that both eth0 and eth1 have been picked up, so all well. In the example output above, we can see that both eth0 and eth1 have been picked up, so all well.
 +
 +<WRAP info>
 +**NOTE:**  Ensure that all interfaces are shown.  If not, then revisit the above config changes around the network.
 +</WRAP>
 +
  
 ---- ----
secure_ubuntu_system/initial_setup.1590010721.txt.gz · Last modified: 2020/07/15 09:30 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki