2. Linux From Scratch 12.3
3. chapter09_networkd
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:empty

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	Linux From Scratch 12.3/chapter09_networkd — Chinese (Simplified Han script)	If you will not use <command>systemd-networkd</command> for network configuration (for example, when the system is not connected to network, or you want to use another utility like NetworkManager for network configuration), disable a service to prevent an error message during boot:
	Linux From Scratch 12.3/chapter09_networkd — Chinese (Simplified Han script)	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 you are in the chroot environment</emphasis>.
	Linux From Scratch 12.3/chapter09_networkd — Chinese (Simplified Han script)	To disable systemd-resolved, issue the following command:
	Linux From Scratch 12.3/chapter09_networkd — Chinese (Simplified Han script)	<userinput>systemctl disable systemd-resolved</userinput>
	Linux From Scratch 12.3/chapter09_networkd — Chinese (Simplified Han script)	When using <command>systemd-resolved</command> for DNS configuration, it creates the file <filename>/run/systemd/resolve/stub-resolv.conf</filename>. And, if <filename>/etc/resolv.conf</filename> does not exist, it will be created by <command>systemd-resolved</command> as a symlink to <filename>/run/systemd/resolve/stub-resolv.conf</filename>. So it's unnecessary to create a <filename>/etc/resolv.conf</filename> manually.
	Linux From Scratch 12.3/chapter09_networkd — Chinese (Simplified Han script)	If the computer is to be visible to the Internet, a valid FQDN can be the domain name itself, or a string resulted by concatenating a prefix (often the hostname) and the domain name with a <quote>.</quote> character. And, you need to contact the domain provider to resolve the FQDN to your public IP address.
	Linux From Scratch 12.3/chapter09_networkd — Chinese (Simplified Han script)	Even if the computer is not visible to the Internet, a FQDN is still needed for certain programs, such as MTAs, to operate properly. A special FQDN, <literal>localhost.localdomain</literal>, can be used for this purpose.
	Linux From Scratch 12.3/chapter09_networkd — Chinese (Simplified Han script)	The <filename>/etc/hostname</filename> does not contain entries for <literal>localhost</literal>, <literal>localhost.localdomain</literal>, or the hostname (without a domain) because they are handled by the <systemitem class='library'>myhostname</systemitem> NSS module, read the man page <ulink role='man' url='&man;nss-myhostname.8'>nss-myhostname(8)</ulink> for details.