diff --git a/chapter09/bootscripts.xml b/chapter09/bootscripts.xml index 57c6377ff..cb88a9fd8 100644 --- a/chapter09/bootscripts.xml +++ b/chapter09/bootscripts.xml @@ -24,7 +24,7 @@ <para>The LFS-Bootscripts package contains a set of scripts to start/stop - the LFS system at bootup/shutdown. + the LFS system at bootup/shutdown. The configuration files and procedures needed to customize the boot process are described in the following sections.</para> diff --git a/chapter09/consoled.xml b/chapter09/consoled.xml index 76d304d44..1425f0410 100644 --- a/chapter09/consoled.xml +++ b/chapter09/consoled.xml @@ -25,7 +25,7 @@ language-specific HOWTOs can also help with this, see <ulink url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. Examine the output of <command>localectl list-keymaps</command> for a list of - valid console keymaps. Look in the + valid console keymaps. Look in the <filename class="directory">/usr/share/consolefonts</filename> directory for valid screen fonts.</para> diff --git a/chapter09/introduction.xml b/chapter09/introduction.xml index 875003f14..7bd2219fc 100644 --- a/chapter09/introduction.xml +++ b/chapter09/introduction.xml @@ -29,7 +29,7 @@ additional scripts that perform the tasks required to initialize the system.</para> - <para>The <command>init</command> program is controlled by the + <para>The <command>init</command> program is controlled by the <filename>/etc/inittab</filename> file and is organized into run levels that can be run by the user:</para> @@ -61,10 +61,10 @@ <itemizedlist> <listitem> - <para>May be slower to boot. A medium speed base LFS system - takes 8-12 seconds where the boot time is measured from the - first kernel message to the login prompt. Network - connectivity is typically established about 2 seconds + <para>May be slower to boot. A medium speed base LFS system + takes 8-12 seconds where the boot time is measured from the + first kernel message to the login prompt. Network + connectivity is typically established about 2 seconds after the login prompt.</para> </listitem> diff --git a/chapter09/locale.xml b/chapter09/locale.xml index 73de29bd7..65cffc570 100644 --- a/chapter09/locale.xml +++ b/chapter09/locale.xml @@ -80,7 +80,7 @@ LC_ALL=<locale name> locale int_prefix</userinput></screen> encoding used by the locale, the local currency, and the prefix to dial before the telephone number in order to get into the country. If any of the commands above fail with a message similar to the one shown below, this means - that your locale was either not installed in Chapter 8 or is not + that your locale was either not installed in Chapter 8 or is not supported by the default installation of Glibc.</para> <screen><computeroutput>locale: Cannot set LC_* to default locale: No such file or directory</computeroutput></screen> @@ -142,7 +142,7 @@ EOF</userinput></screen> substitutes them with question marks in that locale. Also, an attempt to send mail with such characters from Mutt or Pine results in non-RFC-conforming messages being sent (the charset in the outgoing mail is indicated as <quote>unknown - 8-bit</quote>). It's suggested that you use the <quote>C</quote> locale only + 8-bit</quote>). It's suggested that you use the <quote>C</quote> locale only if you are certain that you will never need 8-bit characters.</para> <!-- diff --git a/chapter09/network.xml b/chapter09/network.xml index 45cd1d438..52eb35c18 100644 --- a/chapter09/network.xml +++ b/chapter09/network.xml @@ -31,7 +31,7 @@ will 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 <command>ip link</command> or <command>ls - /sys/class/net</command> after you have booted your system. + /sys/class/net</command> after you have booted your system. </para></note> <para>The following command creates a sample file for the @@ -157,21 +157,21 @@ EOF</userinput></screen> <indexterm zone="ch-config-hosts"> <primary sortas="e-/etc/hosts">/etc/hosts</primary> </indexterm> - + <indexterm zone="ch-config-hosts"> <primary sortas="d-localnet">localnet</primary> <secondary>/etc/hosts</secondary> </indexterm> - + <indexterm zone="ch-config-hosts"> <primary sortas="d-network">network</primary> <secondary>/etc/hosts</secondary> </indexterm> - + <para>Decide on the IP address, fully-qualified domain name (FQDN), and possible aliases for use in the <filename>/etc/hosts</filename> file. The syntax is:</para> - + <screen><literal>IP_address myhost.example.org aliases</literal></screen> <para>Unless the computer is to be visible to the Internet (i.e., there is @@ -186,13 +186,13 @@ EOF</userinput></screen> <para>x can be any number in the range 16-31. y can be any number in the range 0-255.</para> - + <para>A valid private IP address could be 192.168.1.1. A valid FQDN for this IP could be lfs.example.org.</para> - + <para>Even if not using a network card, a valid FQDN is still required. This is necessary for certain programs to operate correctly.</para> - + <para>Create the <filename>/etc/hosts</filename> file by running:</para> <screen><userinput>cat > /etc/hosts << "EOF" @@ -209,7 +209,7 @@ ff02::2 ip6-allrouters EOF</userinput></screen> <para>The <replaceable><192.168.1.1></replaceable>, - <replaceable><FQDN></replaceable>, and + <replaceable><FQDN></replaceable>, and <replaceable><HOSTNAME></replaceable> 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 diff --git a/chapter09/networkd.xml b/chapter09/networkd.xml index 49d4031a0..9090596c0 100644 --- a/chapter09/networkd.xml +++ b/chapter09/networkd.xml @@ -38,7 +38,7 @@ <filename class="extension">.link</filename>, <filename class="extension">.netdev</filename> and <filename class="extension">.network</filename> files. For detailed - descriptions and example contents of these configuration files, consult + descriptions and example contents of these configuration files, consult the <filename>systemd-link(5)</filename>, <filename>systemd-netdev(5)</filename> and <filename>systemd-network(5)</filename> manual pages.</para> @@ -57,7 +57,7 @@ For most systems, there is only one network interface for each type of connection. For example, the classic interface name for a wired connection is eth0. A wireless connection - will usually have the name wifi0 or wlan0. + will usually have the name wifi0 or wlan0. </para> <para> @@ -75,8 +75,8 @@ <listitem> <para> Create a manual naming scheme, for example by naming the - interfaces something like "internet0", "dmz0", or "lan0". - To do that, create .link files in /etc/systemd/network/ that + interfaces something like "internet0", "dmz0", or "lan0". + To do that, create .link files in /etc/systemd/network/ that select an explicit name or a better naming scheme for your network interfaces. For example: </para> @@ -91,13 +91,13 @@ Name=ether0</literal> EOF</userinput></screen> <para> - See the man page systemd.link(5) for more information. + See the man page systemd.link(5) for more information. </para> </listitem> <listitem> <para> - In /boot/grub/grub.cfg, pass the option net.ifnames=0 on the + In /boot/grub/grub.cfg, pass the option net.ifnames=0 on the kernel command line. </para> </listitem> @@ -209,7 +209,7 @@ EOF</userinput></screen> with the IP address of the DNS server most appropriate for your setup. There will often be more than one entry (requirements demand secondary servers for fallback capability). If you only need or want one DNS server, - remove the second <emphasis>nameserver</emphasis> line from the file. + remove the second <emphasis>nameserver</emphasis> line from the file. The IP address may also be a router on the local network. Another option is to use the Google Public DNS service using the IP addresses below as nameservers.</para> @@ -252,12 +252,12 @@ EOF</userinput></screen> <indexterm zone="ch-config-hosts"> <primary sortas="e-/etc/hosts">/etc/hosts</primary> </indexterm> - + <indexterm zone="ch-config-hosts"> <primary sortas="d-localnet">localnet</primary> <secondary>/etc/hosts</secondary> </indexterm> - + <indexterm zone="ch-config-hosts"> <primary sortas="d-network">network</primary> <secondary>/etc/hosts</secondary> diff --git a/chapter09/profile.xml b/chapter09/profile.xml index ec39d3a30..e47153830 100644 --- a/chapter09/profile.xml +++ b/chapter09/profile.xml @@ -103,7 +103,7 @@ LC_ALL=<locale name> locale int_prefix</userinput></screen> encoding used by the locale, the local currency, and the prefix to dial before the telephone number in order to get into the country. If any of the commands above fail with a message similar to the one shown below, this means - that your locale was either not installed in <xref linkend="ch-system-glibc"/> + that your locale was either not installed in <xref linkend="ch-system-glibc"/> or is not supported by the default installation of Glibc.</para> <screen><computeroutput>locale: Cannot set LC_* to default locale: No such file or directory</computeroutput></screen> 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 - + The traditional naming scheme using eth0, eth1, etc can be - restored by adding net.ifnames=0 on the + restored by adding net.ifnames=0 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 . Creating Custom Udev Rules - + 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: @@ -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. - + 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. - + 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: - + SUBSYSTEM=="net" - This tells udev to ignore @@ -106,7 +106,7 @@ udev will assign to this interface. - + The value of NAME 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 NAME value when diff --git a/chapter09/systemd-custom.xml b/chapter09/systemd-custom.xml index 7e0613df2..bab18eb6d 100644 --- a/chapter09/systemd-custom.xml +++ b/chapter09/systemd-custom.xml @@ -50,13 +50,13 @@ EOF Disabling tmpfs for /tmp By default, /tmp is created as - a tmpfs. If this is not desired, it can be overridden by executing the + a tmpfs. If this is not desired, it can be overridden by executing the following command: ln -sfv /dev/null /etc/systemd/system/tmp.mount Alternatively, if a separate partition for - /tmp is desired, specify that + /tmp is desired, specify that partition in a /etc/fstab entry. @@ -81,9 +81,9 @@ EOF systemd-tmpfiles-setup-dev.service systemd-tmpfiles-setup.service - + The system location for the configuration files is - /usr/lib/tmpfiles.d/*.conf. The local + /usr/lib/tmpfiles.d/*.conf. The local configuration files are in /etc/tmpfiles.d. Files in /etc/tmpfiles.d override @@ -94,9 +94,9 @@ EOF Note that the syntax for the - /usr/lib/tmpfiles.d/*.conf files can be + /usr/lib/tmpfiles.d/*.conf files can be confusing. For example, the default deletion of files in the /tmp directory - is located in /usr/lib/tmpfiles.d/tmp.conf with + is located in /usr/lib/tmpfiles.d/tmp.conf with the line: q /tmp 1777 root root 10d @@ -148,7 +148,7 @@ EOF Rather than plain shell scripts used in SysVinit or BSD style init systems, systemd uses a unified format for different types of startup files (or units). The command systemctl is used to - enable, disable, control state, and obtain status of unit files. Here + enable, disable, control state, and obtain status of unit files. Here are some examples of frequently used commands: diff --git a/chapter09/udev.xml b/chapter09/udev.xml index 20b311284..a2ff35511 100644 --- a/chapter09/udev.xml +++ b/chapter09/udev.xml @@ -119,7 +119,7 @@ rule for the device it is creating, it will leave the permissions and ownership at whatever devtmpfs used initially. - + Module Loading @@ -223,12 +223,12 @@ Note that the softdep command also allows pre: dependencies, or a mixture of both - pre: and post: dependencies. See + pre: and post: dependencies. See the modprobe.d(5) manual page for more information on softdep syntax and capabilities. - If the module in question is not a wrapper and is - useful by itself, configure the modules bootscript to + If the module in question is not a wrapper and is + useful by itself, configure the modules bootscript to load this module on system boot. To do this, add the module name to the /etc/sysconfig/modules file on a separate line. This works for wrapper modules too, but is suboptimal in that case. diff --git a/chapter09/usage.xml b/chapter09/usage.xml index d59b38b29..ffb31055d 100644 --- a/chapter09/usage.xml +++ b/chapter09/usage.xml @@ -24,7 +24,7 @@ system to another, so it cannot be assumed that because things worked in one particular Linux distribution, they should work the same in LFS too. LFS has its own way of doing things, but it respects generally accepted standards. - + SysVinit (which will be referred to as init from now on) works using a run-levels scheme. There are seven (numbered 0 to 6) run-levels (actually, there are more run-levels, but they are for special cases and are @@ -233,7 +233,7 @@ EOF <device> is an absolute path in /dev or /sys such as /dev/sr0 or /sys/class/rtc. - For information on kernel module loading and udev, see + For information on kernel module loading and udev, see . @@ -535,28 +535,28 @@ EOF Creating Files at Boot - + File creation at boot configuring - + At times, it is desirable to create files at boot time. For instance, the /tmp/.ICE-unix directory is often needed. This can be done by creating an entry in the /etc/sysconfig/createfiles configuration script. - The format of this file is embedded in the comments of the default + The format of this file is embedded in the comments of the default configuration file. Configuring the sysklogd Script - + sysklogd configuring - + The sysklogd script invokes the syslogd program as a part of System V initialization. The -m 0 option turns off the periodic timestamp mark that @@ -574,11 +574,11 @@ EOF The rc.site File - + rc.site - + The optional /etc/sysconfig/rc.site file contains settings that are automatically set for each SystemV boot script. It can alternatively set the values specified in the hostname, @@ -587,33 +587,33 @@ EOF associated variables are present in both these separate files and rc.site, the values in the script specific files have precedence. - + rc.site also contains parameters that can customize other aspects of the boot process. Setting the IPROMPT variable will enable selective running of bootscripts. Other options are described in the file comments. The default version of the file is as follows: - + &site; - + Customizing the Boot and Shutdown Scripts - + The LFS boot scripts boot and shut down a system in a fairly efficient manner, but there are a few tweaks that you can make in the rc.site file to improve speed even more and to adjust messages according to your preferences. To do this, adjust the settings in the /etc/sysconfig/rc.site file above. - + - + During the boot script udev, there is a call to udev settle that requires some time to complete. This time may or may not be required depending on devices present in the system. If you only have simple partitions and a single ethernet card, the boot process will probably not need to wait for this command. To skip it, set the variable OMIT_UDEV_SETTLE=y. - + The boot script udev_retry also runs udev settle by default. This command is only needed by default if the /var directory is @@ -622,12 +622,12 @@ EOF also need to wait for udev to complete, but in many installations it is not needed. Skip the command by setting the variable OMIT_UDEV_RETRY_SETTLE=y. - + By default, the file system checks are silent. This can appear to be a delay during the bootup process. To turn on the fsck output, set the variable VERBOSE_FSCK=y. - + When rebooting, you may want to skip the filesystem check, fsck, completely. To do this, either create the file /fastboot or reboot the system with the command @@ -636,17 +636,17 @@ EOF /forcefsck or running shutdown with the -F parameter instead of -f. - + Setting the variable FASTBOOT=y will disable fsck during the boot process until it is removed. This is not recommended on a permanent basis. - + Normally, all files in the /tmp directory are deleted at boot time. Depending on the number of files or directories present, this can cause a noticeable delay in the boot process. To skip removing these files set the variable SKIPTMPCLEAN=y. - + During shutdown, the init program sends a TERM signal to each program it has started (e.g. agetty), waits for a set time (default 3 seconds), and sends each process a KILL signal and waits @@ -658,9 +658,9 @@ EOF -t0 -r now). The delay for the sendsignals script can be skipped by setting the parameter KILLDELAY=0. - + - +