Changes in / [8f3b8fa4:c87aec2]

Files:

• appendices/dependencies.xml (modified) (3 diffs)
• chapter09/network.xml (modified) (1 diff)
• chapter09/networkd.xml (modified) (1 diff)

appendices/dependencies.xml

@@ -443 +443 @@
         <seglistitem>
           <seg>Bash, Binutils, Coreutils, GCC, Gettext, Glibc, GMP, Grep,
-          Libcap, Make, OpenSSL, Patch, Perl, Sed, and Texinfo</seg>
+          Libcap, Make, Patch, Perl, Sed, and Texinfo</seg>
         </seglistitem>
       </segmentedlist>
@@ -2306 +2306 @@
       </segmentedlist>
 
-<!-- Begin OpenSSL dependency info -->
-  <bridgehead renderas="sect2" id="openssl-dep">OpenSSL</bridgehead>
+<!-- Begin Openssl dependency info -->
+  <bridgehead renderas="sect2" id="openssl-dep">Openssl</bridgehead>
 
       <segmentedlist id="openssl-depends">
@@ -2333 +2333 @@
         <segtitle>&before;</segtitle>
         <seglistitem>
-          <seg>Coreutils and Linux</seg>
+          <seg>Linux</seg>
         </seglistitem>
       </segmentedlist>

chapter09/network.xml

@@ -28 +28 @@
     the filename be <emphasis>ifconfig</emphasis>.</para>
 
-    <note>
-      <para>If the procedure in the previous section was not used, udev
-      will assign network card interface names based on system physical
-      characteristics such as enp2s1. If you are not sure what your interface
-      name is, you can always run <command>ip link</command> or <command>ls
-      /sys/class/net</command> after you have booted your system.
-      </para>
-
-      <para>The interface names depend on the implementation and
-      configuration of the udev daemon running on the system.  The udev
-      daemon for LFS (installed in <xref linkend="ch-system-eudev"/>) will
-      not run until the LFS system is booted.  So it's unreliable to
-      determine the interface names being used in LFS system by running
-      those commands on the host distro,
-      <emphasis>even though in the chroot environment</emphasis>.</para>
-    </note>
+    <note><para>If the procedure in the previous section was not used, udev
+    will assign network card interface names based on system physical
+    characteristics such as enp2s1. If you are not sure what your interface
+    name is, you can always run <command>ip link</command> or <command>ls
+    /sys/class/net</command> after you have booted your system.
+    </para></note>
 
     <para>The following command creates a sample file for the

chapter09/networkd.xml

@@ -54 +54 @@
       </para>
 
-      <note>
-        <para>The interface names depend on the implementation and
-        configuration of the udev daemon running on the system.  The udev
-        daemon for LFS (<command>systemd-udevd</command>, installed in
-        <xref linkend="ch-system-systemd"/>) will not run unless the LFS
-        system is booted.  So it's unreliable to determine the interface
-        names being used in LFS system by running those commands on the host
-        distro,
-        <emphasis>even though in the chroot environment</emphasis>.</para>
-      </note>
-
       <para>
         For most systems, there is only one network interface for