Remove obsolete pages from the chapter07 directory:

Those have been included into "usage.xml" or obsoleted for a long time now,
and just clobber the sources.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11551 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

6 files changed, 0 insertions, 702 deletions

diff --git a/chapter07/console.xml b/chapter07/console.xml
deleted file mode 100644
index d2562760f..000000000
--- a/chapter07/console.xml
+++ /dev/null
@@ -1,325 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-scripts-console">
-  <?dbhtml filename="console.html"?>
-
-  <title>Configuring the Linux Console</title>
-
-  <indexterm zone="ch-scripts-console">
-    <primary sortas="d-console">console</primary>
-    <secondary>configuring</secondary>
-  </indexterm>
-
-  <para>This section discusses how to configure the <command>console</command>
-  bootscript that sets up the keyboard map, console font and console kernel log
-  level. If non-ASCII characters (e.g., the copyright sign, the British pound
-  sign and Euro symbol) will not be used and the keyboard is a U.S. one, much
-  of this section can be skipped. Without the configuration file, (or
-  equivalent settings in <filename>rc.site</filename>), the
-  <command>console</command> bootscript will do nothing.</para>
-
-  <sect2 id="ch-scripts-sysv-console">
-    <title>System V</title>
-
-  <para>The <command>console</command> script reads the
-  <filename>/etc/sysconfig/console</filename> file for configuration
-  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"/>. If still in
-  doubt, look in the <filename class="directory">/usr/share/keymaps</filename> 
-  and <filename class="directory">/usr/share/consolefonts</filename> directories
-  for valid keymaps and screen fonts. Read <filename>loadkeys(1)</filename> and
-  <filename>setfont(8)</filename> manual pages to determine the correct
-  arguments for these programs.</para>
-
-  <para>The <filename>/etc/sysconfig/console</filename> file should contain lines
-  of the form: VARIABLE="value". The following variables are recognized:</para>
-
-  <variablelist>
-
-    <varlistentry>
-      <term>LOGLEVEL</term>
-      <listitem>
-        <para>This variable specifies the log level for kernel messages sent
-        to the console as set by <command>dmesg</command>. Valid levels are
-        from "1" (no messages) to "8". The default level is "7".</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>KEYMAP</term>
-      <listitem>
-        <para>This variable specifies the arguments for the
-        <command>loadkeys</command> program, typically, the name of keymap
-        to load, e.g., <quote>es</quote>. If this variable is not set, the
-        bootscript will not run the <command>loadkeys</command> program,
-        and the default kernel keymap will be used.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>KEYMAP_CORRECTIONS</term>
-      <listitem>
-        <para>This (rarely used) variable
-        specifies the arguments for the second call to the
-        <command>loadkeys</command> program. This is useful if the stock keymap
-        is not completely satisfactory and a small adjustment has to be made. E.g.,
-        to include the Euro sign into a keymap that normally doesn't have it,
-        set this variable to <quote>euro2</quote>.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>FONT</term>
-      <listitem>
-        <para>This variable specifies the arguments for the
-        <command>setfont</command> program. Typically, this includes the font
-        name, <quote>-m</quote>, and the name of the application character
-        map to load. E.g., in order to load the <quote>lat1-16</quote> font
-        together with the <quote>8859-1</quote> application character map
-        (as it is appropriate in the USA),
-        <!-- because of the copyright sign -->
-        set this variable to <quote>lat1-16 -m 8859-1</quote>.
-        In UTF-8 mode, the kernel uses the application character map for
-        conversion of composed 8-bit key codes in the keymap to UTF-8, and thus
-        the argument of the "-m" parameter should be set to the encoding of the
-        composed key codes in the keymap.</para>
-
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>UNICODE</term>
-      <listitem>
-        <para>Set this variable to <quote>1</quote>, <quote>yes</quote> or
-        <quote>true</quote> in order to put the
-        console into UTF-8 mode. This is useful in UTF-8 based locales and
-        harmful otherwise.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>LEGACY_CHARSET</term>
-      <listitem>
-        <para>For many keyboard layouts, there is no stock Unicode keymap in
-        the Kbd package. The <command>console</command> bootscript will
-        convert an available keymap to UTF-8 on the fly if this variable is
-        set to the encoding of the available non-UTF-8 keymap.</para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
-
-  <para>Some examples:</para>
-
-  <itemizedlist>
-
-    <listitem>
-      <para>For a non-Unicode setup, only the KEYMAP and FONT variables are
-      generally needed. E.g., for a Polish setup, one would use:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/console
-
-KEYMAP="pl2"
-FONT="lat2a-16 -m 8859-2"
-
-# End /etc/sysconfig/console</literal>
-EOF</userinput></screen>
-    </listitem>
-
-    <listitem>
-      <para>As mentioned above, it is sometimes necessary to adjust a
-      stock keymap slightly. The following example adds the Euro symbol to the
-      German keymap:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/console
-
-KEYMAP="de-latin1"
-KEYMAP_CORRECTIONS="euro2"
-FONT="lat0-16 -m 8859-15"
-
-# End /etc/sysconfig/console</literal>
-EOF</userinput></screen>
-    </listitem>
-
-    <listitem>
-      <para>The following is a Unicode-enabled example for Bulgarian, where a
-      stock UTF-8 keymap exists:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/console
-
-UNICODE="1"
-KEYMAP="bg_bds-utf8"
-FONT="LatArCyrHeb-16"
-
-# End /etc/sysconfig/console</literal>
-EOF</userinput></screen>
-    </listitem>
-
-    <listitem>
-      <para>Due to the use of a 512-glyph LatArCyrHeb-16 font in the previous
-      example, bright colors are no longer available on the Linux console unless
-      a framebuffer is used. If one wants to have bright colors without
-      framebuffer and can live without characters not belonging to his language,
-      it is still possible to use a language-specific 256-glyph font, as
-      illustrated below:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/console
-
-UNICODE="1"
-KEYMAP="bg_bds-utf8"
-FONT="cyr-sun16"
-
-# End /etc/sysconfig/console</literal>
-EOF</userinput></screen>
-    </listitem>
-
-    <listitem>
-      <para>The following example illustrates keymap autoconversion from
-      ISO-8859-15 to UTF-8 and enabling dead keys in Unicode mode:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/console
-
-UNICODE="1"
-KEYMAP="de-latin1"
-KEYMAP_CORRECTIONS="euro2"
-LEGACY_CHARSET="iso-8859-15"
-FONT="LatArCyrHeb-16 -m 8859-15"
-
-# End /etc/sysconfig/console</literal>
-EOF</userinput></screen>
-    </listitem>
-
-    <listitem>
-      <para>Some keymaps have dead keys (i.e., keys that don't produce a
-      character by themselves, but put an accent on the character produced
-      by the next key) or define composition rules (such as: <quote>press
-      Ctrl+. A E to get &AElig;</quote> in the default keymap).
-      Linux-&linux-version; interprets dead keys and composition rules in the
-      keymap correctly only when the source characters to be composed together
-      are not multibyte. This deficiency doesn't affect keymaps for European
-      languages, because there accents are added to unaccented ASCII
-      characters, or two ASCII characters are composed together. However, in
-      UTF-8 mode it is a problem, e.g., for the Greek language, where one
-      sometimes needs to put an accent on the letter <quote>alpha</quote>.
-      The solution is either to avoid the use of UTF-8, or to install the
-      X window system that doesn't have this limitation in its input
-      handling.</para>
-    </listitem>
-
-    <listitem>
-      <para>For Chinese, Japanese, Korean and some other languages, the Linux
-      console cannot be configured to display the needed characters. Users
-      who need such languages should install the X Window System, fonts that
-      cover the necessary character ranges, and the proper input method (e.g.,
-      SCIM, it supports a wide variety of languages).</para>
-    </listitem>
-
-  </itemizedlist>
-
-  <!-- Added because folks keep posting their console file with X questions
-  to blfs-support list -->
-  <note>
-    <para>The <filename>/etc/sysconfig/console</filename> file only controls
-    the Linux text console localization. It has nothing to do with setting
-    the proper keyboard layout and terminal fonts in the X Window System, with
-    ssh sessions or with a serial console. In such situations, limitations
-    mentioned in the last two list items above do not apply.</para>
-  </note>
-
-  </sect2>
-
-  <sect2 id="ch-scripts-systemd-console">
-    <title>Systemd</title>
-
-  <indexterm zone="ch-scripts-systemd-console">
-    <primary sortas="d-console">systemd console</primary>
-    <secondary>configuring</secondary>
-  </indexterm>
-
-  <para>This section discusses how to configure the
-  <command>systemd-vconsole-setup</command> system service, which configures
-  the virtual console font and console keymap.</para>
-
-  <para>The <command>systemd-vconsole-setup</command> service reads the
-  <filename>/etc/vconsole.conf</filename> file for configuration
-  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
-  <filename class="directory">/usr/share/consolefonts</filename>
-  directory for valid screen fonts.</para>
-
-  <para>The <filename>/etc/vconsole.conf</filename> file should contain lines
-  of the form: VARIABLE="value". The following variables are recognized:</para>
-
-  <variablelist>
-
-    <varlistentry>
-      <term>KEYMAP</term>
-      <listitem>
-        <para>This variable specifies the key mapping table for the keyboard. If
-        unset, it defaults to <literal>us</literal>.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>KEYMAP_TOGGLE</term>
-      <listitem>
-        <para>This variable can be used to configure a second toggle keymap and
-        is unset by default.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>FONT</term>
-      <listitem>
-        <para>This variable specifies the font used by the virtual
-        console.</para>
-      </listitem>
-    </varlistentry>
-    <varlistentry>
-      <term>FONT_MAP</term>
-      <listitem>
-        <para>This variable specifies the console map to be used.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>FONT_UNIMAP</term>
-      <listitem>
-        <para>This variable specifies the Unicode font map.</para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
-
-  <para>An example for a German keyboard and console is given below:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/vconsole.conf &lt;&lt; "EOF"
-<literal>KEYMAP=de-latin1
-FONT=Lat2-Terminus16</literal>
-EOF</userinput></screen>
-
-  <para>You can change KEYMAP value at runtime by using the
-  <command>localectl</command> utility:</para>
-
-<screen role="nodump"><userinput>localectl set-keymap MAP</userinput></screen>
-
-  <note><para>Please note that <command>localectl</command> command can
-  be used  only on a system booted with Systemd.</para></note>
-
-  </sect2>
-
-</sect1>
diff --git a/chapter07/hostname.xml b/chapter07/hostname.xml
deleted file mode 100644
index 07de15e98..000000000
--- a/chapter07/hostname.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-scripts-hostname">
-  <?dbhtml filename="hostname.html"?>
-
-  <title>Configuring the system hostname</title>
-
-  <indexterm zone="ch-scripts-hostname">
-    <primary sortas="d-hostname">hostname</primary>
-    <secondary>configuring</secondary>
-  </indexterm>
-
-  <para>During the boot process, both Systemd and System V use the same
-  file for establishing the system's hostname.  This needs to be configured by
-  creating <filename>/etc/hostname</filename>.</para>
-
-  <para>Create the <filename>/etc/hostname</filename> file and enter a
-  hostname by running:</para>
-
-<screen><userinput>echo "<replaceable>&lt;lfs&gt;</replaceable>" &gt; /etc/hostname</userinput></screen>
-
-  <para><replaceable>&lt;lfs&gt;</replaceable> 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 <filename>/etc/hosts</filename> file.</para>
-
-</sect1>
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 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-scripts-hosts">
-  <?dbhtml filename="hosts.html"?>
-
-  <title>Customizing the /etc/hosts File</title>
-
-  <indexterm zone="ch-scripts-hosts">
-    <primary sortas="e-/etc/hosts">/etc/hosts</primary>
-  </indexterm>
-
-  <indexterm zone="ch-scripts-hosts">
-    <primary sortas="d-localnet">localnet</primary>
-  <secondary>/etc/hosts</secondary></indexterm>
-
-  <indexterm zone="ch-scripts-hosts">
-    <primary sortas="d-network">network</primary>
-  <secondary>/etc/hosts</secondary></indexterm>
-
-  <para>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
-  <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 a registered domain and a valid block of assigned IP
-  addresses&mdash;most users do not have this), make sure that the IP
-  address is in the private network IP address range. Valid ranges
-  are:</para>
-
-<screen><literal>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</literal></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 &gt; /etc/hosts &lt;&lt; "EOF"
-<literal># Begin /etc/hosts (network card version)
-
-127.0.0.1 localhost
-<replaceable>&lt;192.168.1.1&gt;</replaceable> <replaceable>&lt;HOSTNAME.example.org&gt;</replaceable> <replaceable>[alias1] [alias2 ...]</replaceable>
-
-# End /etc/hosts (network card version)</literal>
-EOF</userinput></screen>
-
-  <para>The <replaceable>&lt;192.168.1.1&gt;</replaceable> and
-  <replaceable>&lt;HOSTNAME.example.org&gt;</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 existing network). The optional alias
-  name(s) can be omitted.</para>
-
-  <para>If a network card is not going to be configured, create the
-  <filename>/etc/hosts</filename> file by running:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
-<literal># Begin /etc/hosts (no network card version)
-
-127.0.0.1 <replaceable>&lt;HOSTNAME.example.org&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable> localhost
-
-# End /etc/hosts (no network card version)</literal>
-EOF</userinput></screen>
-
-</sect1>
diff --git a/chapter07/setclock.xml b/chapter07/setclock.xml
deleted file mode 100644
index 729c447f6..000000000
--- a/chapter07/setclock.xml
+++ /dev/null
@@ -1,132 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-scripts-clock">
-  <?dbhtml filename="clock.html"?>
-
-  <title>Configuring the System Clock</title>
-
-  <para>Procedures for setting the system clock differ between systemd and 
-  System V, however the separate procedures do not conflict so both
-  procedures should be accomplished to allow switching between systems.</para>
-
-  <sect2 id="ch-scripts-setclock">
-    <title>System V Clock Configuration</title>
-
-    <indexterm zone="ch-scripts-setclock">
-      <primary sortas="d-setclock">setclock</primary>
-    <secondary>configuring</secondary></indexterm>
-
-    <para>The <command>setclock</command> script reads the time from the hardware
-    clock, also known as the BIOS or the Complementary Metal Oxide Semiconductor
-    (CMOS) clock. If the hardware clock is set to UTC, this script will convert the
-    hardware clock's time to the local time using the
-    <filename>/etc/localtime</filename> file (which tells the
-    <command>hwclock</command> program which timezone the user is in). There is no
-    way to detect whether or not the hardware clock is set to UTC, so this
-    needs to be configured manually.</para>
-
-    <para>The <command>setclock</command> is run via
-    <application>udev</application> when the kernel detects the hardware
-    capability upon boot.  It can also be run manually with the stop parameter to
-    store the system time to the CMOS clock.</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>
-    command. This will display what the current time is according to the hardware
-    clock. If this time matches whatever your watch says, then the hardware clock is
-    set to local time. If the output from <command>hwclock</command> is not local
-    time, chances are it is set to UTC time. Verify this by adding or subtracting
-    the proper amount of hours for the timezone to the time shown by
-    <command>hwclock</command>. For example, if you are currently in the MST
-    timezone, which is also known as GMT -0700, add seven hours to the local
-    time.</para>
-
-    <para>Change the value of the <envar>UTC</envar> variable below
-    to a value of <parameter>0</parameter> (zero) if the hardware clock
-    is <emphasis>not</emphasis> set to UTC time.</para>
-
-    <para>Create a new file <filename>/etc/sysconfig/clock</filename> by running
-    the following:</para>
-
-<screen><userinput>cat &gt; /etc/sysconfig/clock &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/clock
-
-UTC=1
-
-# Set this to any options you might need to give to hwclock,
-# such as machine hardware clock type for Alphas.
-CLOCKPARAMS=
-
-# End /etc/sysconfig/clock</literal>
-EOF</userinput></screen>
-
-    <para>A good hint explaining how to deal with time on LFS is available
-    at <ulink url="&hints-root;time.txt"/>. It explains issues such as
-    time zones, UTC, and the <envar>TZ</envar> environment variable.</para>
-
-    <note><para>The CLOCKPARAMS and UTC paramaters may be alternatively set
-    in the <filename>/etc/sysconfig/rc.site</filename> file.</para></note>
-
-  </sect2>
-
-  <sect2 id="ch-scripts-systemd-clock">
-    <title>Systemd Clock Configuration</title>
-
-  <indexterm zone="ch-scripts-clock">
-    <primary sortas="d-clock">clock</primary>
-  <secondary>configuring</secondary></indexterm>
-
-  <para>This section discusses how to configure the
-  <command>systemd-timedated</command> system service, which configures
-  system clock and timezone.</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 local time.  Create the
-  <filename>/etc/adjtime</filename> file with the following contents <emphasis>if your
-  hardware clock is set to local time</emphasis>:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/adjtime &lt;&lt; "EOF"
-<literal>0.0 0 0.0
-0
-LOCAL</literal>
-EOF</userinput></screen>
-
-    <para>If <filename>/etc/adjtime</filename> isn't present at first boot,
-    <command>systemd-timedated</command> will assume that hardware clock is
-    set to UTC and create the file using that setting.</para>
-
-    <para>You can also use the <command>timedatectl</command> utility to tell
-    <command>systemd-timedated</command> if your hardware clock is set to
-    UTC or local time:</para>
-
-<screen role="nodump"><userinput>timedatectl set-local-rtc 1</userinput></screen>
-
-    <para><command>timedatectl</command> can also be used to change system time and
-    time zone.</para>
-
-    <para>To change your current system time, issue:</para>
-
-<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>To change your current time zone, issue:</para>
-
-<screen role="nodump"><userinput>timedatectl set-timezone TIMEZONE</userinput></screen>
-
-    <para>You can get list of available time zones by running:</para>
-
-<screen role="nodump"><userinput>timedatectl list-timezones</userinput></screen>
-
-    <note><para>Please note that <command>timedatectl</command> command can
-    be used only on a system booted with Systemd.</para></note>
-
-  </sect2>
-
-</sect1>
diff --git a/chapter07/site.xml b/chapter07/site.xml
deleted file mode 100644
index 1dd6df9a1..000000000
--- a/chapter07/site.xml
+++ /dev/null
@@ -1,103 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  <!ENTITY site               SYSTEM "../appendices/rc.site.script">
-  %general-entities;
-]>
-
-<sect1 id="ch-scripts-site">
-  <?dbhtml filename="site.html"?>
-
-  <title>The rc.site File</title>
-
-  <indexterm zone="ch-scripts-site">
-    <primary sortas="a-rc.site">rc.site</primary>
-  </indexterm>
-
-  <para>The optional <filename>/etc/sysconfig/rc.site</filename> file contains
-  settings that are automatically set for each SystemV boot script.  It can
-  alternatively set the values specified in the <filename>hostname</filename>,
-  <filename>console</filename>, and <filename>clock</filename> files in the
-  <filename class='directory'>/etc/sysconfig/</filename> directory.  If the
-  associated variables are present in both these separate files and
-  <filename>rc.site</filename>, the values in the script specific files have
-  precedence. </para>
-
-  <para><filename>rc.site</filename> 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:</para>
-
-  <!-- Use role to fix a pdf generation problem -->
-  <screen role="auto">&site;</screen>
-
-  <sect2>
-    <title>Customizing the Boot and Shutdown Scripts</title>
-
-    <para>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 <filename>/etc/sysconfig/rc.site</filename> file above.</para>
-
-    <itemizedlist>
-
-    <listitem><para>During the boot script <filename>udev</filename>, there is
-    a call to <command>udev settle</command> 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.</para></listitem>
-
-    <listitem><para>The boot script <filename>udev_retry</filename> also runs
-    <command>udev settle</command> by default.  This command is only needed by
-    default if the <filename class='directory'>/var</filename> directory is
-    separately mounted.  This is because the clock needs the file
-    <filename>/var/lib/hwclock/adjtime</filename>.  Other customizations may
-    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.
-    </para></listitem>
-
-    <listitem><para>By default, the file system checks are silent.  This can
-    appear to be a delay during the bootup process.  To turn on the
-    <command>fsck</command> output, set the variable VERBOSE_FSCK=y.
-    </para></listitem>
-
-    <listitem><para>When rebooting, you may want to skip the filesystem check,
-    <command>fsck</command>, completely.  To do this, either create the file
-    <filename>/fastboot</filename> or reboot the system with the command
-    <command>/sbin/shutdown -f -r now</command>.  On the other hand, you can
-    force all file systems to be checked by creating
-    <filename>/forcefsck</filename> or running <command>shutdown</command> with
-    the <parameter>-F</parameter> parameter instead of <parameter>-f</parameter>.
-    </para>
-
-    <para>Setting the variable FASTBOOT=y will disable <command>fsck</command>
-    during the boot process until it is removed.  This is not recommended
-    on a permanent basis.</para></listitem>
-
-    <listitem><para>Normally, all files in the <filename
-    class='directory'>/tmp</filename> 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.</para></listitem>
-
-    <listitem><para>During shutdown, the <command>init</command> 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
-    again.  This process is repeated in the <command>sendsignals</command>
-    script for any processes that are not shut down by their own scripts.  The
-    delay for <command>init</command> can be set by passing a parameter.  For
-    example to remove the delay in <command>init</command>, pass the -t0
-    parameter when shutting down or rebooting (e.g.  <command>/sbin/shutdown
-    -t0 -r now</command>).  The delay for the  <command>sendsignals</command>
-    script can be skipped by setting the parameter
-    KILLDELAY=0.</para></listitem>
-
-    </itemizedlist>
-
-  </sect2>
-
-</sect1>
-
diff --git a/chapter07/sysklogd.xml b/chapter07/sysklogd.xml
deleted file mode 100644
index a3747478a..000000000
--- a/chapter07/sysklogd.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-scripts-sysklogd">
-  <?dbhtml filename="sysklogd.html"?>
-
-  <title>Configuring the sysklogd Script</title>
-
-  <indexterm zone="ch-scripts-sysklogd">
-    <primary sortas="d-sysklogd">sysklogd</primary>
-    <secondary>configuring</secondary>
-  </indexterm>
-
-  <para>The <filename>sysklogd</filename> script invokes the
-  <command>syslogd</command> program as a part of System V initialization.  The
-  <parameter>-m 0</parameter> option turns off the periodic timestamp mark that
-  <command>syslogd</command> writes to the log files every 20 minutes by
-  default.  If you want to turn on this periodic timestamp mark, edit
-  <filename>/etc/sysconfig/rc.site</filename> and define the variable
-  SYSKLOGD_PARMS to the desired value.  For instance, to remove all parameters,
-  set the variable to a null value:</para>
-
-<screen role="nodump">SYSKLOGD_PARMS=</screen>
-
-  <para>See <userinput>man syslogd</userinput> for more options.</para>
-
-</sect1>