- Timestamp:
- 12/22/2017 08:18:46 PM (6 years ago)
- 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, 8.2, 8.3, 8.4, 9.0, 9.1, 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:
- 3b4e848
- Parents:
- 896e77e
- Location:
- chapter07
- Files:
-
- 2 edited
-
networkd.xml (modified) (3 diffs)
-
systemd-custom.xml (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
chapter07/networkd.xml
r896e77e r94e3e7bd 44 44 <filename>systemd-network(5)</filename> manual pages.</para> 45 45 46 <note><para>Udev may assign network card interface names based 47 on system physical characteristics such as enp2s1. If you are 48 not sure what your interface name is, you can always run 49 <command>ip link</command> after you have booted your system. 50 </para></note> 46 <sect3 id="systemd-network-devices"> 47 <title>Network Device Naming</title> 48 49 <para> 50 Udev normally assigns network card interface names based 51 on system physical characteristics such as enp2s1. If you are 52 not sure what your interface name is, you can always run 53 <command>ip link</command> after you have booted your system. 54 </para> 55 56 <para> 57 For most systems, there is only one network interface for 58 each type of connection. For example, the classic interface 59 name for a wired connection is eth0. A wireless connection 60 will usually have the name wifi0 or wlan0. 61 </para> 62 63 <para> 64 If you prefer to use the classic or customized network interface names, 65 there are three alternative ways to do that:</para> 66 67 <itemizedlist> 68 <listitem> 69 <para> 70 Mask udev's .link file for the default policy: 71 <screen role="nodump"><userinput>ln -s /dev/null /etc/systemd/network/99-default.link</userinput></screen> 72 </para> 73 </listitem> 74 75 <listitem> 76 <para> 77 Create a manual naming scheme, for example by naming the 78 interfaces something like "internet0", "dmz0", or "lan0". 79 For that, create .link 80 files in /etc/systemd/network/, that choose an explicit name or a 81 better naming scheme for one, some, or all of your interfaces. 82 For example: 83 </para> 84 85 <screen role="nodump"><userinput>cat > /etc/systemd/network/10-ether0.link << "EOF" 86 <literal>[Match] 87 # Change the MAC address as appropriate for your network device 88 MACAddress=12:34:45:78:90:AB 89 90 [Link] 91 Name=ether0</literal> 92 EOF</userinput></screen> 93 94 <para> 95 See the man page systemd.link(5) for more information. 96 </para> 97 </listitem> 98 99 <listitem> 100 <para> 101 In /boot/grub/grub.cfg, pass the option net.ifnames=0 on the 102 kernel command line. 103 </para> 104 </listitem> 105 </itemizedlist> 106 </sect3> 51 107 52 108 <sect3 id="systemd-networkd-static"> … … 57 113 systemd-resolved):</para> 58 114 59 <screen><userinput>cat > /etc/systemd/network/10-eth 0-static.network << "EOF"115 <screen><userinput>cat > /etc/systemd/network/10-eth-static.network << "EOF" 60 116 <literal>[Match] 61 Name= eth0117 Name=<network-device-name> 62 118 63 119 [Network] … … 80 136 DHCP setup:</para> 81 137 82 <screen role="nodump"><userinput>cat > /etc/systemd/network/10-eth 0-dhcp.network << "EOF"138 <screen role="nodump"><userinput>cat > /etc/systemd/network/10-eth-dhcp.network << "EOF" 83 139 <literal>[Match] 84 Name= eth0140 Name=<network-device-name> 85 141 86 142 [Network] -
chapter07/systemd-custom.xml
r896e77e r94e3e7bd 54 54 <screen role="nodump"><userinput>ln -sfv /dev/null /etc/systemd/system/tmp.mount</userinput></screen> 55 55 56 <para>This is not necessary if there is a separate partition for 57 <filename class="directory">/tmp</filename> specified in 58 <filename>/etc/fstab</filename>.</para> 56 <para>Alternatively, if a a separate partition for 57 <filename class="directory">/tmp</filename> is desired, specify that 58 partition in an <filename>/etc/fstab</filename> entry.</para> 59 60 <warning> 61 <para> 62 Do not create the symbolic link above if a separate partition is used 63 for <filename class="directory">/tmp</filename>. This will prvent the 64 root file system (/) from being remounted r/w and make the system 65 unusable when booted. 66 </para> 67 </warning> 59 68 60 69 </sect2> … … 81 90 <filename>tmpfiles.d(5)</filename> manual page for file format 82 91 details.</para> 92 93 <para> 94 Note that the syntax for the 95 <filename>/usr/lib/tmpfiles.d/*.conf</filename> files can be 96 confusing. For example, the default deletion of files in the /tmp directory 97 is located in <filename>/usr/lib/tmpfiles.d/tmp.conf</filename> with 98 the line: 99 100 <screen role="nodump">q /tmp 1777 root root 10d</screen> 101 102 The type field, q, discusses creating a subvolume with quotas which 103 is really only applicable to btrfs filesystems. It references type v 104 which in turn references type d (directory). This then creates the 105 specified directory if is is not present and adjusts the permissions 106 and ownership as specified. Contents of the directory will be 107 subject to time based cleanup if the age argument is specified. 108 </para> 109 110 <para> 111 If the default parameters are not desired, then the file should 112 be copied to <filename class="directory">/etc/tmpfiles.d</filename> 113 and edited as desired. For example: 114 115 <screen role="nodump"><userinput>mkdir -p /etc/tempfiles.d 116 cp /usr/lib/tmpfiles.d/tmp.conf /etc/tempfiles.d</userinput></screen> 117 </para> 83 118 84 119 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.
