Index: chapter09/bootscripts.xml
===================================================================
--- chapter09/bootscripts.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/bootscripts.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -25,5 +25,5 @@
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.
Index: chapter09/consoled.xml
===================================================================
--- chapter09/consoled.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/consoled.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -26,5 +26,5 @@
url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>.
Examine the output of localectl list-keymaps for a list of
- valid console keymaps. Look in the
+ valid console keymaps. Look in the
/usr/share/consolefonts
directory for valid screen fonts.
Index: chapter09/introduction.xml
===================================================================
--- chapter09/introduction.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/introduction.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -30,5 +30,5 @@
system.
- The init program is controlled by the
+ The init program is controlled by the
/etc/inittab file and is organized into run levels that
can be run by the user:
@@ -62,8 +62,8 @@
- 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
+ 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.
Index: chapter09/locale.xml
===================================================================
--- chapter09/locale.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/locale.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -81,5 +81,5 @@
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.
@@ -143,5 +143,5 @@
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 unknown
- 8-bit
). It's suggested that you use the C
locale only
+ 8-bit). It's suggested that you use the C
locale only
if you are certain that you will never need 8-bit characters.
Index: chapter09/network.xml
===================================================================
--- chapter09/network.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/network.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -32,5 +32,5 @@
characteristics such as enp2s1. If you are not sure what your interface
name is, you can always run ip link or ls
- /sys/class/net after you have booted your system.
+ /sys/class/net after you have booted your system.
@@ -158,19 +158,19 @@
/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
@@ -187,11 +187,11 @@
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:
@@ -210,5 +210,5 @@
The <192.168.1.1>,
- <FQDN>, and
+ <FQDN>, and
<HOSTNAME> values need to be
changed for specific uses or requirements (if assigned an IP address by a
Index: chapter09/networkd.xml
===================================================================
--- chapter09/networkd.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/networkd.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -39,5 +39,5 @@
.netdev and
.network files. For detailed
- descriptions and example contents of these configuration files, consult
+ descriptions and example contents of these configuration files, consult
the systemd-link(5),
systemd-netdev(5) and
@@ -58,5 +58,5 @@
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.
@@ -76,6 +76,6 @@
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:
@@ -92,5 +92,5 @@
- See the man page systemd.link(5) for more information.
+ See the man page systemd.link(5) for more information.
@@ -98,5 +98,5 @@
- 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.
@@ -210,5 +210,5 @@
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 nameserver line from the file.
+ remove the second nameserver 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
@@ -253,10 +253,10 @@
/etc/hosts
-
+
localnet
/etc/hosts
-
+
network
Index: chapter09/profile.xml
===================================================================
--- chapter09/profile.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/profile.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -104,5 +104,5 @@
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
+ that your locale was either not installed in
or is not supported by the default installation of Glibc.
Index: chapter09/symlinks.xml
===================================================================
--- chapter09/symlinks.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/symlinks.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -23,5 +23,5 @@
and the Realtek card becomes eth1. In some cases, after a reboot the cards
could get renumbered the other way around.
-
+
In the new naming scheme, typical network device names would then
be something like enp5s0 or wlp3s0. If this naming convention is not
@@ -31,12 +31,12 @@
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 .
@@ -44,5 +44,5 @@
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.
@@ -62,5 +62,5 @@
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
@@ -70,9 +70,9 @@
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:
-
+
@@ -107,5 +107,5 @@
-
+
The value of NAME is the important part. Make sure
you know which name has been assigned to each of your network cards before
Index: chapter09/systemd-custom.xml
===================================================================
--- chapter09/systemd-custom.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/systemd-custom.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -51,5 +51,5 @@
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:
@@ -57,5 +57,5 @@
Alternatively, if a separate partition for
- /tmp is desired, specify that
+ /tmp is desired, specify that
partition in a /etc/fstab entry.
@@ -82,7 +82,7 @@
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
@@ -95,7 +95,7 @@
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:
@@ -149,5 +149,5 @@
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:
Index: chapter09/udev.xml
===================================================================
--- chapter09/udev.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/udev.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -120,5 +120,5 @@
ownership at whatever devtmpfs used initially.
-
+
Module Loading
@@ -224,10 +224,10 @@
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.
Index: chapter09/usage.xml
===================================================================
--- chapter09/usage.xml (revision df732b51c063da5200ac0ce648cf284f67596125)
+++ chapter09/usage.xml (revision c34b4fb1c6ba28636f5743572367aaa754479d44)
@@ -25,5 +25,5 @@
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
@@ -234,5 +234,5 @@
/sys/class/rtc.
- For information on kernel module loading and udev, see
+ For information on kernel module loading and udev, see
.
@@ -536,15 +536,15 @@
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.
@@ -552,10 +552,10 @@
Configuring the sysklogd Script
-
+
sysklogd
configuring
-
+
The sysklogd script invokes the
syslogd program as a part of System V initialization. The
@@ -575,9 +575,9 @@
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
@@ -588,16 +588,16 @@
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
@@ -605,7 +605,7 @@
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
@@ -614,5 +614,5 @@
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
@@ -623,10 +623,10 @@
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
@@ -637,9 +637,9 @@
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.
@@ -647,5 +647,5 @@
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
@@ -659,7 +659,7 @@
script can be skipped by setting the parameter
KILLDELAY=0.
-
+
-
+