Changeset 9e7475a for chapter09/networkd.xml

Timestamp:

06/12/2020 09:04:48 PM (4 years ago)

Author:

Douglas R. Reno <renodr@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

4234aea6

Parents:

a3d0817

Message:

Updates to chapter09 for systemd

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/cross2@11929 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter09/networkd.xml (modified) (9 diffs)

chapter09/networkd.xml

@@ -49 +49 @@
       <para>
         Udev normally assigns network card interface names based
-        on system physical characteristics such as enp2s1. If you are
+        on physical system characteristics such as enp2s1. If you are
         not sure what your interface name is, you can always run
         <command>ip link</command> after you have booted your system.
@@ -77 +77 @@
              Create a manual naming scheme, for example by naming the
              interfaces something like "internet0", "dmz0", or "lan0". 
-             For that, create .link
-             files in /etc/systemd/network/, that choose an explicit name or a
-             better naming scheme for one, some, or all of your interfaces. 
-             For example:
+             To do that, create .link files in /etc/systemd/network/ that 
+             select an explicit name or a better naming scheme for your
+             network interfaces. For example:
           </para>
 
@@ -171 +170 @@
       <note><para>If using another means to configure your network
       interfaces (ex: ppp, network-manager, etc.), or if using any type of
-      local resolver (ex: bind, dnsmasq, etc.), or any other software that
-      generates an <filename>/etc/resolv.conf</filename> (ex: resolvconf), the
-      <command>systemd-resolved</command> service should not be
+      local resolver (ex: bind, dnsmasq, unbound, etc.), or any other software 
+      that generates an <filename>/etc/resolv.conf</filename> (ex: resolvconf),
+      the <command>systemd-resolved</command> service should not be
       used.</para></note>
 
@@ -207 +206 @@
       <para>Replace
       <replaceable>&lt;IP address of the nameserver&gt;</replaceable>
-      with the IP address of the DNS most appropriate for the setup. There will
-      often be more than one entry (requirements demand secondary servers for
-      fallback capability). If you only need or want one DNS server, remove the
-      second <emphasis>nameserver</emphasis> line from the file. The IP address
-      may also be a router on the local network.</para>
+      with the IP address of the DNS server most appropriate for your setup.
+      There will often be more than one entry (requirements demand secondary
+      servers for fallback capability). If you only need or want one DNS server,
+      remove the second <emphasis>nameserver</emphasis> line from the file. 
+      The IP address may also be a router on the local network. Another option
+      is to use the Google Public DNS service using the IP addresses below as
+      nameservers.</para>
 
       <note><para>The Google Public IPv4 DNS addresses are
@@ -263 +264 @@
 
      <para>Decide on a fully-qualified domain name (FQDN), and possible aliases
-     for use in the <filename>/etc/hosts</filename> file. If using static
+     for use in the <filename>/etc/hosts</filename> file. If using static IP
      addresses, you'll also need to decide on an IP address. The syntax
      for a hosts file entry is:</para>
@@ -286 +287 @@
 
      <para>Even if not using a network card, a valid FQDN is still required.
-     This is necessary for certain programs to operate correctly.</para>
-
-     <para>If using DHCP, DHCPv6, IPv6 Autoconfiguration, or if a network card
-     is not going to be configured, create the <filename>/etc/hosts</filename>
-     file by running the following command:</para>
+     This is necessary for certain programs, such as MTAs, to operate properly.</para>
+
+     <para>Create the /etc/hosts file using the following command:</para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
@@ -308 +307 @@
      specifically for the FQDN.</para>
 
+<!--
      <para>If using a static address, create the <filename>/etc/hosts</filename>
      file by running this command instead:</para>
@@ -314 +314 @@
 <literal># Begin /etc/hosts
 
-127.0.0.1 localhost
+127.0.0.1 localhost.localdomain localhost
 127.0.1.1 <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable>
 <replaceable>&lt;192.168.0.2&gt;</replaceable> <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable> <replaceable>[alias1] [alias2] ...</replaceable>
@@ -330 +330 @@
      network/system administrator and the machine will be connected to an
      existing network). The optional alias name(s) can be omitted.</para>
-   
+-->
    </sect2>