Changeset c34b4fb for chapter09/symlinks.xml
- Timestamp:
- 09/07/2021 08:01:10 PM (3 years ago)
- 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:
- 9cea9a2
- Parents:
- df732b5
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter09/symlinks.xml
rdf732b5 rc34b4fb 23 23 and the Realtek card becomes eth1. In some cases, after a reboot the cards 24 24 could get renumbered the other way around.</para> 25 25 26 26 <para>In the new naming scheme, typical network device names would then 27 27 be something like enp5s0 or wlp3s0. If this naming convention is not … … 31 31 <sect3> 32 32 <title>Disabling Persistent Naming on the Kernel Command Line</title> 33 33 34 34 <para>The traditional naming scheme using eth0, eth1, etc can be 35 restored by adding <userinput>net.ifnames=0</userinput> on the 35 restored by adding <userinput>net.ifnames=0</userinput> on the 36 36 kernel command line. This is most appropriate for those systems 37 37 that have only one ethernet device of the same type. Laptops 38 often have multiple ethernet connections that are named eth0 and 39 wlan0 and are also candidates for this method. The command line 40 is passed in the GRUB configuration file. 38 often have multiple ethernet connections that are named eth0 and 39 wlan0 and are also candidates for this method. The command line 40 is passed in the GRUB configuration file. 41 41 See <xref linkend="grub-cfg"/>.</para> 42 42 </sect3> … … 44 44 <sect3> 45 45 <title>Creating Custom Udev Rules</title> 46 46 47 47 <para>The naming scheme can be customized by creating custom udev 48 48 rules. A script has been included that generates the initial rules. … … 62 62 are not consistently assigned. In these cases, this method cannot 63 63 be used.</para></note> 64 64 65 65 <para>The file begins with a comment block followed by two lines for each 66 66 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 71 71 udev rule that matches this NIC and actually assigns it a name.</para> 72 72 73 73 <para>All udev rules are made up of several keys, separated by commas and 74 74 optional whitespace. This rule's keys and an explanation of each of them 75 75 are as follows:</para> 76 76 77 77 <itemizedlist> 78 78 <listitem> … … 107 107 </listitem> 108 108 </itemizedlist> 109 109 110 110 <para>The value of <literal>NAME</literal> is the important part. Make sure 111 111 you know which name has been assigned to each of your network cards before
Note:
See TracChangeset
for help on using the changeset viewer.