Changeset d4c8dce4 for chapter09/symlinks.xml

Timestamp:

09/15/2021 07:24:40 AM (3 years ago)

Author:

Pierre Labastie <pierre.labastie@…>

Branches:

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, 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:

9af096e

Parents:

df1207e (diff), 06e7b361 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Merge branch 'trunk' into plabs/condxml

File:

• chapter09/symlinks.xml (modified) (6 diffs)

chapter09/symlinks.xml

@@ -23 +23 @@
     and the Realtek card becomes eth1. In some cases, after a reboot the cards
     could get renumbered the other way around.</para>
-    
+
     <para>In the new naming scheme, typical network device names would then
     be something like enp5s0 or wlp3s0.  If this naming convention is not
@@ -31 +31 @@
     <sect3>
       <title>Disabling Persistent Naming on the Kernel Command Line</title>
-   
+
       <para>The traditional naming scheme using eth0, eth1, etc can be
-      restored by adding <userinput>net.ifnames=0</userinput> on the 
+      restored by adding <userinput>net.ifnames=0</userinput> on the
       kernel command line.  This is most appropriate for those systems
       that have only one ethernet device of the same type.  Laptops
-      often have multiple ethernet connections that are named eth0 and 
-      wlan0 and are also candidates for this method.  The command line 
-      is passed in the GRUB configuration file. 
+      often have multiple ethernet connections that are named eth0 and
+      wlan0 and are also candidates for this method.  The command line
+      is passed in the GRUB configuration file.
       See <xref linkend="grub-cfg"/>.</para>
     </sect3>
@@ -44 +44 @@
     <sect3>
       <title>Creating Custom Udev Rules</title>
-   
+
       <para>The naming scheme can be customized by creating custom udev
       rules.  A script has been included that generates the initial rules.
@@ -62 +62 @@
       are not consistently assigned.  In these cases, this method cannot
       be used.</para></note>
-  
+
       <para>The file begins with a comment block followed by two lines for each
       NIC. The first line for each NIC is a commented description showing its
@@ -70 +70 @@
       interface; this information is only for reference. The second line is the
       udev rule that matches this NIC and actually assigns it a name.</para>
-  
+
       <para>All udev rules are made up of several keys, separated by commas and
       optional whitespace. This rule's keys and an explanation of each of them
       are as follows:</para>
-  
+
       <itemizedlist>
         <listitem>
@@ -107 +107 @@
         </listitem>
       </itemizedlist>
-  
+
       <para>The value of <literal>NAME</literal> is the important part. Make sure
       you know which name has been assigned to each of your network cards before