diff --git a/chapter07/chapter07.xml b/chapter07/chapter07.xml
index de0f65c83..0b620104d 100644
--- a/chapter07/chapter07.xml
+++ b/chapter07/chapter07.xml
@@ -14,10 +14,8 @@
-
-
diff --git a/chapter07/hostname.xml b/chapter07/hostname.xml
deleted file mode 100644
index c26b2dc2b..000000000
--- a/chapter07/hostname.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
- %general-entities;
-]>
-
-
-
-
- Configuring the system hostname
-
-
- hostname
- configuring
-
-
- Systemd reads /etc/hostname to determine which
- hostname should be set.
-
- Create the /etc/hostname file and enter a
- hostname by running:
-
-echo "<lfs>" > /etc/hostname
-
- <lfs> needs to be replaced with the name given
- to the computer. Do not enter the Fully Qualified Domain Name (FQDN) here. That
- information is put in the /etc/hosts file.
-
-
diff --git a/chapter07/hosts.xml b/chapter07/hosts.xml
deleted file mode 100644
index 13c0ccbbf..000000000
--- a/chapter07/hosts.xml
+++ /dev/null
@@ -1,80 +0,0 @@
-
-
- %general-entities;
-]>
-
-
-
-
- Customizing the /etc/hosts File
-
-
- /etc/hosts
-
-
-
- localnet
- /etc/hosts
-
-
- network
- /etc/hosts
-
- If a network card is to be configured, decide on the IP address,
- fully-qualified domain name (FQDN), and possible aliases for use in the
- /etc/hosts file. The syntax is:
-
-IP_address myhost.example.org aliases
-
- Unless the computer is to be visible to the Internet (i.e.,
- there is a registered domain and a valid block of assigned IP
- addresses—most users do not have this), make sure that the IP
- address is in the private network IP address range. Valid ranges
- are:
-
-Private Network Address Range Normal Prefix
-10.0.0.1 - 10.255.255.254 8
-172.x.0.1 - 172.x.255.254 16
-192.168.y.1 - 192.168.y.254 24
-
- x can be any number in the range 16-31. y can be any number in
- the range 0-255.
-
- A valid private IP address could be 192.168.1.1. A valid FQDN for this
- IP could be lfs.example.org.
-
- Even if not using a network card, a valid FQDN is still required.
- This is necessary for certain programs to operate correctly.
-
- Create the /etc/hosts file by running:
-
-cat > /etc/hosts << "EOF"
-# Begin /etc/hosts (network card version)
-
-127.0.0.1 localhost
-<192.168.1.1> <HOSTNAME.example.org> [alias1] [alias2 ...]
-
-# End /etc/hosts (network card version)
-EOF
-
- The <192.168.1.1> and
- <HOSTNAME.example.org>
- values need to be changed for specific uses or requirements (if
- assigned an IP address by a network/system administrator and the
- machine will be connected to an existing network). The optional alias
- name(s) can be omitted.
-
- If a network card is not going to be configured, create the
- /etc/hosts file by running:
-
-cat > /etc/hosts << "EOF"
-# Begin /etc/hosts (no network card version)
-
-127.0.0.1 <HOSTNAME.example.org> <HOSTNAME> localhost
-
-# End /etc/hosts (no network card version)
-EOF
-
-
diff --git a/chapter07/network.xml b/chapter07/network.xml
index 49d4594e2..69bc96176 100644
--- a/chapter07/network.xml
+++ b/chapter07/network.xml
@@ -18,94 +18,72 @@
configured.
- Creating Network Interface Configuration Files
+ Network Interface Configuration Files
- Which interfaces are brought up and down by the network script
- depends on the files in /etc/sysconfig/. This directory should
- contain a file for each interface to be configured, such as
- ifconfig.xyz, where xyz
is
- required to be a Network Card Interface name (e.g. eth0).
- Inside this file are attributes to this interface, such as its IP
- address(es), subnet masks, and so forth. It is necessary that
- the stem of the filename be ifconfig.
+ Starting with version 209, systemd ships a network configuration
+ daemon called systemd-networkd which can be used for
+ basic network configuration.
- Udev may assign random Network Card Interface names
- for some network cards such as enp2s1. If you are not sure what
- your Network Card Interface name is, you can always run
- ip l after you have booted your system. Again,
- it is important that ifconfig.xyz is named
- after correct Network Card Interface name (e.g.
- ifconfig.enp2s1 or
- ifconfig.eth0) or Systemd will fail to bring
- up your network interface.
+ Configuration files for systemd-networkd can be
+ placed in /usr/lib/systemd/network
+ or /etc/systemd/network. Note that
+ files in /etc/systemd/network have
+ higher priority than the ones in
+ /usr/lib/systemd/network.
- The following command creates a sample file for the
- eth0 device with a static IP address:
+ There are three types of configuration files:
+ .link,
+ .netdev and
+ .network files. For detailed
+ explanation about contents of the mentioned
+ configuration files, consult systemd-link(5),
+ systemd-netdev(5) and
+ systemd-network(5) manual pages.
-cd /etc/sysconfig/
-cat > ifconfig.eth0 << "EOF"
-IFACE=eth0
-SERVICE=ipv4-static
-IP=192.168.1.1
-GATEWAY=192.168.1.2
-PREFIX=24
-BROADCAST=192.168.1.255
+ Udev may assign network card interface names based
+ on system physical characteristics such as enp2s1. If you are
+ not sure what your interface name is, you can always run
+ ip link after you have booted your system.
+
+
+
+ Static IP Configuration
+
+ The command below creates a basic configuration file for
+ Static IP setup:
+
+cat > /etc/systemd/network/10-static-eth0.network << "EOF"
+[Match]
+Name=eth0
+
+[Network]
+Address=192.168.0.2/24
+Gateway=192.168.0.1
+DNS=192.168.0.1
EOF
- The values of these variables must be changed in every file to match
- the proper setup.
+ More than one DNS entry can be specified in the configuration file.
- The IFACE variable defines the interface name,
- for example, eth0. It is required for all network device configuration
- files.
+
- The SERVICE variable defines the method used for
- obtaining the IP address. The LFS-Network-Scripts package has a modular
- IP assignment format, and creating additional files in the /lib/services/ directory allows other IP
- assignment methods. This is commonly used for Dynamic Host Configuration
- Protocol (DHCP), which is addressed in the BLFS book.
+
+ DHCP Configuration
- The GATEWAY variable should contain the default
- gateway IP address, if one is present. If not, then comment out the
- variable entirely.
+ The command below creates a basic configuration file for
+ DHCP setup:
- The PREFIX variable contains the number of
- bits used in the subnet. Each octet in an IP address is 8 bits. If the
- subnet's netmask is 255.255.255.0, then it is using the first three octets
- (24 bits) to specify the network number. If the netmask is 255.255.255.240,
- it would be using the first 28 bits. Prefixes longer than 24 bits are
- commonly used by DSL and cable-based Internet Service Providers (ISPs).
- In this example (PREFIX=24), the netmask is 255.255.255.0. Adjust the
- PREFIX variable according to your specific subnet.
- If omitted, the PREFIX defaults to 24.
+cat > /etc/systemd/network/10-dhcp-eth0.network << "EOF"
+[Match]
+Name=eth0
- For more information see the ifup man page.
+[Network]
+DHCP=yes
+EOF
-
+ Note that systemd-networkd can only handle
+ DHCPv4. DHCPv6 support is a work in progress.
-
- Configuring the Network Interface Card at boot
-
- Enabling of the Network Interface Card configuration is
- done per interface. To enable Network Interface Card
- configuration at boot, run:
-
-systemctl enable ifupdown@eth0
-
- To disable previously enabled Network Interface
- Card configuration at boot, run:
-
-systemctl disable ifupdown@eth0
-
- To manually start the Network Interface Card configuration,
- run:
-
-systemctl start ifupdown@eth0
-
- Replace eth0 with the correct Network Interface Card
- name as described on the beginning of this page.
+
@@ -121,8 +99,19 @@ EOF
resolve Internet domain names to IP addresses, and vice versa. This is
best achieved by placing the IP address of the DNS server, available
from the ISP or network administrator, into
- /etc/resolv.conf. Create the file by running the
- following:
+ /etc/resolv.conf.
+
+ When using systemd-networkd for network
+ configuration, another daemon, systemd-resolved,
+ is responsible for creating the /etc/resolv.conf
+ file. It is, however, placed in a non-standard location which is
+ writable since early boot, so it is necessary to create a symlink
+ to it by running the following command:
+
+ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf
+
+ If static /etc/resolv.conf is desired, create
+ it by running the following command:
cat > /etc/resolv.conf << "EOF"
# Begin /etc/resolv.conf
@@ -149,4 +138,99 @@ EOF
+
+ Configuring the system hostname
+
+
+ hostname
+ configuring
+
+
+ During the boot process, the file /etc/hostname
+ is used for establishing the system's hostname.
+
+ Create the /etc/hostname file and enter a
+ hostname by running:
+
+echo "<lfs>" > /etc/hostname
+
+ <lfs> needs to be replaced with the
+ name given to the computer. Do not enter the Fully Qualified Domain Name
+ (FQDN) here. That information is put in the
+ /etc/hosts file.
+
+
+
+
+ Customizing the /etc/hosts File
+
+
+ /etc/hosts
+
+
+
+ localnet
+ /etc/hosts
+
+
+
+ network
+ /etc/hosts
+
+
+ Decide on the IP address, fully-qualified domain name (FQDN), and
+ possible aliases for use in the /etc/hosts file. The
+ syntax is:
+
+IP_address myhost.example.org aliases
+
+ Unless the computer is to be visible to the Internet (i.e., there is
+ a registered domain and a valid block of assigned IP addresses—most
+ users do not have this), make sure that the IP address is in the private
+ network IP address range. Valid ranges are:
+
+Private Network Address Range Normal Prefix
+10.0.0.1 - 10.255.255.254 8
+172.x.0.1 - 172.x.255.254 16
+192.168.y.1 - 192.168.y.254 24
+
+ x can be any number in the range 16-31. y can be any number in the
+ range 0-255.
+
+ A valid private IP address could be 192.168.1.1. A valid FQDN for
+ this IP could be lfs.example.org.
+
+ Even if not using a network card, a valid FQDN is still required.
+ This is necessary for certain programs to operate correctly.
+
+ Create the /etc/hosts file by running:
+
+cat > /etc/hosts << "EOF"
+# Begin /etc/hosts (network card version)
+
+127.0.0.1 localhost
+<192.168.0.2> <HOSTNAME.example.org> [alias1] [alias2] ...
+
+# End /etc/hosts (network card version)
+EOF
+
+ The <192.168.0.2> and
+ <HOSTNAME.example.org> values need to be
+ changed for specific uses or requirements (if assigned an IP address by a
+ network/system administrator and the machine will be connected to an
+ existing network). The optional alias name(s) can be omitted.
+
+ If a network card is not going to be configured, create the
+ /etc/hosts file by running:
+
+cat > /etc/hosts << "EOF"
+# Begin /etc/hosts (no network card version)
+
+127.0.0.1 <HOSTNAME.example.org> <HOSTNAME> localhost
+
+# End /etc/hosts (no network card version)
+EOF
+
+
+