Updates to chapter09 for systemd

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11929 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

8 files changed, 71 insertions, 69 deletions

diff --git a/chapter09/clock.xml b/chapter09/clock.xml
index 872ba677c..585017e35 100644
--- a/chapter09/clock.xml
+++ b/chapter09/clock.xml
@@ -16,7 +16,7 @@
 
   <para>This section discusses how to configure the
   <command>systemd-timedated</command> system service, which configures
-  system clock and timezone.</para>
+  the system clock and timezone.</para>
 
   <para>If you cannot remember whether or not the hardware clock is set to UTC,
   find out by running the <userinput>hwclock --localtime --show</userinput>
@@ -30,7 +30,7 @@
   time.</para>
 
   <para><command>systemd-timedated</command> reads <filename>/etc/adjtime</filename>,
-  and depending on the contents of the file, it sets the clock to either UTC or
+  and depending on the contents of the file, sets the clock to either UTC or
   local time.</para>
 
   <para>Create the <filename>/etc/adjtime</filename> file with the following contents
@@ -59,7 +59,7 @@ EOF</userinput></screen>
 
 <screen role="nodump"><userinput>timedatectl set-time YYYY-MM-DD HH:MM:SS</userinput></screen>
 
-  <para>Hardware clock will also be updated accordingly.</para>
+  <para>The hardware clock will also be updated accordingly.</para>
 
   <para>To change your current time zone, issue:</para>
 
diff --git a/chapter09/consoled.xml b/chapter09/consoled.xml
index bf1fdc8e0..76d304d44 100644
--- a/chapter09/consoled.xml
+++ b/chapter09/consoled.xml
@@ -24,8 +24,8 @@
   information. Decide which keymap and screen font will be used. Various
   language-specific HOWTOs can also help with this, see <ulink
   url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>.
-  Examine <command>localectl list-keymaps</command> output for a list of
-  valid console keymaps. Look in
+  Examine the output of <command>localectl list-keymaps</command> for a list of
+  valid console keymaps. Look in the 
   <filename class="directory">/usr/share/consolefonts</filename>
   directory for valid screen fonts.</para>
 
@@ -106,34 +106,34 @@ EOF</userinput></screen>
     <varlistentry>
       <term>list-x11-keymap-models</term>
       <listitem>
-        <para>Show known X11 keyboard mapping models.</para>
+        <para>Shows known X11 keyboard mapping models.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term>list-x11-keymap-layouts</term>
       <listitem>
-        <para>Show known X11 keyboard mapping layouts.</para>
+        <para>Shows known X11 keyboard mapping layouts.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term>list-x11-keymap-variants</term>
       <listitem>
-        <para>Show known X11 keyboard mapping variants.</para>
+        <para>Shows known X11 keyboard mapping variants.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term>list-x11-keymap-options</term>
       <listitem>
-        <para>Show known X11 keyboard mapping options.</para>
+        <para>Shows known X11 keyboard mapping options.</para>
       </listitem>
     </varlistentry>
 
   </variablelist>
 
   <note><para>Using any of the parameters listed above requires the
-  XKeyboard Config package from BLFS.</para></note>
+  XKeyboard-Config package from BLFS.</para></note>
 
 </sect1>
diff --git a/chapter09/etcshells.xml b/chapter09/etcshells.xml
index a0d5f21a8..b9d299c93 100644
--- a/chapter09/etcshells.xml
+++ b/chapter09/etcshells.xml
@@ -28,8 +28,8 @@
 
   <para>For example, this file is consulted by <command>chsh</command>
   to determine whether an unprivileged user may change the login shell for her
-  own account. If the command name is not listed, the user will be denied of
-  change.</para>
+  own account. If the command name is not listed, the user will be denied the
+  ability to change shells.</para>
 
   <para>It is a requirement for applications such as
   <application>GDM</application> which does not populate the
diff --git a/chapter09/introductiond.xml b/chapter09/introductiond.xml
index fa2403edb..f0be70cec 100644
--- a/chapter09/introductiond.xml
+++ b/chapter09/introductiond.xml
@@ -38,7 +38,7 @@
      </listitem>
   </itemizedlist>
 
-  <para>Third, configuring the system clock and keyboard layout.</para>
+  <para>Third, configuring the system clock and keyboard layout is shown.</para>
 
   <itemizedlist>
      <listitem>
@@ -49,9 +49,8 @@
      </listitem>
   </itemizedlist>
 
-
   <para>Fourth, a brief introduction to the scripts and configuration
-  files used when the user logs into the system.</para>
+  files used when the user logs into the system is presented.</para>
 
   <itemizedlist>
      <listitem>
@@ -62,7 +61,7 @@
      </listitem>
   </itemizedlist>
 
-  <para>And finally, configuring the systemd behavior.</para>
+  <para>And finally, configuring the behavior of systemd is discussed.</para>
 
   <itemizedlist>
      <listitem>
diff --git a/chapter09/locale.xml b/chapter09/locale.xml
index 5f473ac72..23442a513 100644
--- a/chapter09/locale.xml
+++ b/chapter09/locale.xml
@@ -14,16 +14,16 @@
     <primary sortas="e-etc-locale-conf">/etc/locale.conf</primary>
   </indexterm>
 
-  <para>The <filename>/etc/locale.conf</filename> below sets some
+  <para>The <filename>/etc/locale.conf</filename> file below sets some
   environment variables necessary for native language support. Setting
   them properly results in:</para>
 
   <itemizedlist>
     <listitem>
-      <para>The output of programs translated into the native language</para>
+      <para>The output of programs being translated into your native language</para>
     </listitem>
     <listitem>
-      <para>Correct classification of characters into letters, digits and other
+      <para>The correct classification of characters into letters, digits and other
       classes. This is necessary for <command>bash</command> to properly accept
       non-ASCII characters in command lines in non-English locales</para>
     </listitem>
@@ -31,15 +31,15 @@
       <para>The correct alphabetical sorting order for the country</para>
     </listitem>
     <listitem>
-      <para>Appropriate default paper size</para>
+      <para>The appropriate default paper size</para>
     </listitem>
     <listitem>
-      <para>Correct formatting of monetary, time, and date values</para>
+      <para>The correct formatting of monetary, time, and date values</para>
     </listitem>
   </itemizedlist>
 
   <para>Replace <replaceable>&lt;ll&gt;</replaceable> below with the two-letter code
-  for the desired language (e.g., <quote>en</quote>) and
+  for your desired language (e.g., <quote>en</quote>) and
   <replaceable>&lt;CC&gt;</replaceable> with the two-letter code for the appropriate
   country (e.g., <quote>GB</quote>). <replaceable>&lt;charmap&gt;</replaceable> should
   be replaced with the canonical charmap for your chosen locale. Optional
@@ -54,7 +54,7 @@
   is also referred to as <quote>iso8859-1</quote> and <quote>iso88591</quote>.
   Some applications cannot handle the various synonyms correctly (e.g., require
   that <quote>UTF-8</quote> is written as <quote>UTF-8</quote>, not
-  <quote>utf8</quote>), so it is safest in most
+  <quote>utf8</quote>), so it is the safest in most
   cases to choose the canonical name for a particular locale. To determine
   the canonical name, run the following command, where <replaceable>&lt;locale
   name&gt;</replaceable> is the output given by <command>locale -a</command> for
@@ -80,8 +80,8 @@ LC_ALL=&lt;locale name&gt; 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&nbsp;6 or is not supported by
-  the default installation of Glibc.</para>
+  that your locale was either not installed in Chapter&nbsp;6 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>
 
@@ -90,7 +90,7 @@ LC_ALL=&lt;locale name&gt; locale int_prefix</userinput></screen>
   Further instructions assume that there are no such error messages from
   Glibc.</para>
 
-  <!-- FIXME: the xlib example will became obsolete real soon -->
+  <!-- FIXME: the xlib example will become obsolete in the future.-->
   <para>Some packages beyond LFS may also lack support for your chosen locale. One
   example is the X library (part of the X Window System), which outputs the
   following error message if the locale does not exactly match one of the character
@@ -142,11 +142,13 @@ 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>). So you can use the <quote>C</quote> locale only if you are sure that
-  you will never need 8-bit characters.</para>
+  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>
 
+<!--
   <para>UTF-8 based locales are not supported well by many programs.
   Work is in progress to document and, if possible, fix such problems, see
   <ulink url="&blfs-book;introduction/locale-issues.html"/>.</para>
+-->
 
 </sect1>
diff --git a/chapter09/networkd.xml b/chapter09/networkd.xml
index 688c315aa..1acc215b9 100644
--- a/chapter09/networkd.xml
+++ b/chapter09/networkd.xml
@@ -48,7 +48,7 @@
 
       <para>
         Udev normally assigns network card interface names based
-        on system physical characteristics such as enp2s1. If you are
+        on physical system characteristics such as enp2s1. If you are
         not sure what your interface name is, you can always run
         <command>ip link</command> after you have booted your system.
       </para>
@@ -76,10 +76,9 @@
           <para>
              Create a manual naming scheme, for example by naming the
              interfaces something like "internet0", "dmz0", or "lan0". 
-             For that, create .link
-             files in /etc/systemd/network/, that choose an explicit name or a
-             better naming scheme for one, some, or all of your interfaces. 
-             For example:
+             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>
 
 <screen role="nodump"><userinput>cat &gt; /etc/systemd/network/10-ether0.link &lt;&lt; "EOF"
@@ -170,9 +169,9 @@ EOF</userinput></screen>
 
       <note><para>If using another means to configure your network
       interfaces (ex: ppp, network-manager, etc.), or if using any type of
-      local resolver (ex: bind, dnsmasq, etc.), or any other software that
-      generates an <filename>/etc/resolv.conf</filename> (ex: resolvconf), the
-      <command>systemd-resolved</command> service should not be
+      local resolver (ex: bind, dnsmasq, unbound, etc.), or any other software 
+      that generates an <filename>/etc/resolv.conf</filename> (ex: resolvconf),
+      the <command>systemd-resolved</command> service should not be
       used.</para></note>
 
       <para>When using <command>systemd-resolved</command> for DNS
@@ -206,11 +205,13 @@ EOF</userinput></screen>
 
       <para>Replace
       <replaceable>&lt;IP address of the nameserver&gt;</replaceable>
-      with the IP address of the DNS most appropriate for the 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. The IP address
-      may also be a router on the local network.</para>
+      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. 
+      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>
 
       <note><para>The Google Public IPv4 DNS addresses are
       <parameter>8.8.8.8</parameter> and <parameter>8.8.4.4</parameter>
@@ -262,7 +263,7 @@ EOF</userinput></screen>
      </indexterm>
 
      <para>Decide on a fully-qualified domain name (FQDN), and possible aliases
-     for use in the <filename>/etc/hosts</filename> file. If using static
+     for use in the <filename>/etc/hosts</filename> file. If using static IP
      addresses, you'll also need to decide on an IP address. The syntax
      for a hosts file entry is:</para>
 
@@ -285,11 +286,9 @@ EOF</userinput></screen>
      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>
+     This is necessary for certain programs, such as MTAs, to operate properly.</para>
 
-     <para>If using DHCP, DHCPv6, IPv6 Autoconfiguration, or if a network card
-     is not going to be configured, create the <filename>/etc/hosts</filename>
-     file by running the following command:</para>
+     <para>Create the /etc/hosts file using the following command:</para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
 <literal># Begin /etc/hosts
@@ -307,13 +306,14 @@ EOF</userinput></screen>
      the IPv6 loopback interface. 127.0.1.1 is a loopback entry reserved
      specifically for the FQDN.</para>
 
+<!--
      <para>If using a static address, create the <filename>/etc/hosts</filename>
      file by running this command instead:</para>
 
 <screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
 <literal># Begin /etc/hosts
 
-127.0.0.1 localhost
+127.0.0.1 localhost.localdomain localhost
 127.0.1.1 <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable>
 <replaceable>&lt;192.168.0.2&gt;</replaceable> <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable> <replaceable>[alias1] [alias2] ...</replaceable>
 ::1       localhost ip6-localhost ip6-loopback
@@ -329,7 +329,7 @@ EOF</userinput></screen>
      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.</para>
-   
+-->
    </sect2>
 
 </sect1>
diff --git a/chapter09/systemd-custom.xml b/chapter09/systemd-custom.xml
index 787fd4572..809c1a273 100644
--- a/chapter09/systemd-custom.xml
+++ b/chapter09/systemd-custom.xml
@@ -49,13 +49,14 @@ EOF</userinput></screen>
     <title>Disabling tmpfs for /tmp</title>
 
     <para>By default, <filename class="directory">/tmp</filename> is created as
-    a tmpfs. If this is not desired, it can be overridden by the following:</para>
+    a tmpfs. If this is not desired, it can be overridden by executing the 
+    following command:</para>
 
 <screen role="nodump"><userinput>ln -sfv /dev/null /etc/systemd/system/tmp.mount</userinput></screen>
 
     <para>Alternatively, if a a separate partition for
     <filename class="directory">/tmp</filename> is desired, specify that 
-    partition in an <filename>/etc/fstab</filename> entry.</para>
+    partition in a <filename>/etc/fstab</filename> entry.</para>
 
     <warning>
       <para>
@@ -87,7 +88,7 @@ EOF</userinput></screen>
     <filename class="directory">/etc/tmpfiles.d</filename> override
     files with the same name in
     <filename class="directory">/usr/lib/tmpfiles.d</filename>. See
-    <filename>tmpfiles.d(5)</filename> manual page  for file format
+    <filename>tmpfiles.d(5)</filename> manual page for file format
     details.</para>
 
     <para>
@@ -103,7 +104,7 @@ EOF</userinput></screen>
       is really only applicable to btrfs filesystems.  It references type v
       which in turn references type d (directory). This then creates the
       specified directory if is is not present and adjusts the permissions
-      and ownership as specified.  Contents of the directory will be
+      and ownership as specified. Contents of the directory will be
       subject to time based cleanup if the age argument is specified.
      </para>
 
@@ -121,7 +122,7 @@ cp /usr/lib/tmpfiles.d/tmp.conf /etc/tmpfiles.d</userinput></screen>
   <sect2>
     <title>Overriding Default Services Behavior</title>
 
-    <para>The parameter of a unit can be overriden by creating a directory
+    <para>The parameters of a unit can be overriden by creating a directory
     and a configuration file in <filename
     class="directory">/etc/systemd/system</filename>. For example:</para>
 
@@ -180,7 +181,7 @@ EOF</userinput></screen>
 
     <para>Logging on a system booted with systemd is handled with
     systemd-journald (by default), rather than a typical unix syslog daemon.
-    You can also add a normal syslog daemon and have both work side by
+    You can also add a normal syslog daemon and have both operate side by
     side if desired. The systemd-journald program stores journal entries in a
     binary format rather than a plain text log file. To assist with
     parsing the file, the command <command>journalctl</command> is provided.
@@ -202,7 +203,7 @@ EOF</userinput></screen>
          chronological order.</para>
        </listitem>
        <listitem>
-         <para><command>journalctl -f</command>: povides functionality similar
+         <para><command>journalctl -f</command>: provides functionality similar
          to tail -f (follow).</para>
        </listitem>
     </itemizedlist>
@@ -215,23 +216,23 @@ EOF</userinput></screen>
     <para>Core dumps are useful to debug crashed programs, especially
     when a daemon process crashes. On systemd booted systems the core
     dumping is handled by <command>systemd-coredump</command>.  It will
-    log the core dump into the journal and store the core dump itself in
+    log the core dump in the journal and store the core dump itself in
     <filename class="directory">/var/lib/systemd/coredump</filename>.
-    To retrieve and process core dumps, <command>coredumpctl</command>
+    To retrieve and process core dumps, the <command>coredumpctl</command>
     tool is provided.  Here are some examples of frequently used commands:
     </para>
 
     <itemizedlist>
       <listitem>
         <para><command>coredumpctl -r</command>: lists all core dumps in
-        reversed chronological order.</para>
+        reverse chronological order.</para>
       </listitem>
       <listitem>
-        <para><command>coredumpctl -1 info</command>: show the information
-        of the last core dump.</para>
+        <para><command>coredumpctl -1 info</command>: shows the information
+        from the last core dump.</para>
       </listitem>
       <listitem>
-        <para><command>coredumpctl -1 debug</command>: load the last core
+        <para><command>coredumpctl -1 debug</command>: loads the last core
         dump into <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
         </para>
       </listitem>
@@ -249,7 +250,7 @@ cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
 MaxUse=5G</literal>
 EOF</userinput></screen>
 
-    <para>See <filename>systemd-coredump(8)</filename>,
+    <para>See the <filename>systemd-coredump(8)</filename>,
     <filename>coredumpctl(1)</filename>, and
     <filename>coredump.conf.d(5)</filename> manual pages for more
     information.</para>
@@ -284,7 +285,7 @@ EOF</userinput></screen>
           advantage of explicitly allowing and disallowing processes to run
           after the user session has ended, but breaks backwards compatibility
           with tools like <command>nohup</command> and utilities that use
-          <function>deamon()</function>.
+          <function>daemon()</function>.
         </para>
       </listitem>
       <listitem>
@@ -298,7 +299,7 @@ EOF</userinput></screen>
       </listitem>
       <listitem>
         <para>
-          <emphasis>Disable at build-time</emphasis>: You can enable
+          <emphasis>Disable at build-time</emphasis>: You can disable
           lingering by default while building systemd by adding the switch
           <parameter>-Ddefault-kill-user-processes=false</parameter> to the
           <command>meson</command> command for systemd. This completely
diff --git a/chapter09/udev.xml b/chapter09/udev.xml
index 508795a03..a3a7c0cf9 100644
--- a/chapter09/udev.xml
+++ b/chapter09/udev.xml
@@ -223,13 +223,13 @@
 
       <para>Note that the <quote>softdep</quote> command also allows
       <literal>pre:</literal> dependencies, or a mixture of both
-      <literal>pre:</literal> and <literal>post:</literal>.  See the
-      <filename>modprobe.d(5)</filename> manual page for more information
+      <literal>pre:</literal> and <literal>post:</literal> dependencies.  See 
+      the <filename>modprobe.d(5)</filename> manual page for more information
       on <quote>softdep</quote> syntax and capabilities.</para>
 
-      <para>If the module in question is not a wrapper and is useful by itself,
-      configure the <command>modules</command> bootscript to load this
-      module on system boot. To do this, add the module name to the
+      <para revision="sysv">If the module in question is not a wrapper and is 
+      useful by itself, configure the <command>modules</command> bootscript to 
+      load this module on system boot. To do this, add the module name to the
       <filename>/etc/sysconfig/modules</filename> file on a separate line.
       This works for wrapper modules too, but is suboptimal in that case.</para>