From c34b4fb1c6ba28636f5743572367aaa754479d44 Mon Sep 17 00:00:00 2001
From: Pierre Labastie <pierre.labastie@neuf.fr>
Date: Tue, 7 Sep 2021 22:01:10 +0200
Subject: Remove spaces at end o lines - chapterO9

---
 chapter09/symlinks.xml | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

(limited to 'chapter09/symlinks.xml')

diff --git a/chapter09/symlinks.xml b/chapter09/symlinks.xml
index c4ddd4eaf..24ebf537d 100644
--- a/chapter09/symlinks.xml
+++ b/chapter09/symlinks.xml
@@ -22,7 +22,7 @@
     Intel and Realtek, the network card manufactured by Intel may become eth0
     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
     desired, the traditional naming scheme or a custom scheme can be
@@ -30,20 +30,20 @@
 
     <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>
 
     <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.
       Generate these rules by running:</para>
@@ -61,7 +61,7 @@
       the network rules file may not have been generated because addresses
       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
       hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card),
@@ -69,11 +69,11 @@
       the hardware ID nor the driver is used to determine which name to give an
       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>
           <para><literal>SUBSYSTEM=="net"</literal> - This tells udev to ignore
@@ -106,7 +106,7 @@
           udev will assign to this interface.</para>
         </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
       proceeding, and be sure to use that <literal>NAME</literal> value when
-- 
cgit v1.2.3-54-g00ecf