* Merged newxml into HEAD

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

1 files changed, 21 insertions, 13 deletions

diff --git a/chapter07/usage.xml b/chapter07/usage.xml
index e0810c403..6fedb31d9 100644
--- a/chapter07/usage.xml
+++ b/chapter07/usage.xml
@@ -1,21 +1,30 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../general.ent">
+  %general-entities;
+]>
 <sect1 id="ch-scripts-usage">
 <title>How does the booting process with these scripts work?</title>
-<?dbhtml filename="usage.html" dir="chapter07"?>
+<?dbhtml filename="usage.html"?>
+
+<indexterm zone="ch-scripts-usage">
+<primary sortas="a-Bootscripts">Bootscripts</primary>
+<secondary>usage</secondary></indexterm>
 
 <para>Linux uses a special booting facility named SysVinit. It's based on a
-concept of <emphasis>runlevels</emphasis>. It can be widely different 
+concept of <emphasis>run-levels</emphasis>. It can be widely different 
 from one system to another, so it can't be assumed that because things 
 worked in &lt;insert distro name&gt; they should work like that in LFS 
 too. LFS has its own way of doing things, but it respects generally 
 accepted standards.</para>
 
 <para>SysVinit (which we'll call <emphasis>init</emphasis> from now on) works 
-using a runlevels scheme. There are 7 (from 0 to 6) runlevels
-(actually, there are more runlevels but they are for special cases and 
+using a run-levels scheme. There are 7 (from 0 to 6) run-levels
+(actually, there are more run-levels but they are for special cases and 
 generally not used. The init man page describes those details), and each 
 one of those corresponds to the things the computer is supposed to do when 
-it starts up. The default runlevel is 3. Here are the descriptions of the 
-different runlevels as they are often implemented:</para>
+it starts up. The default run-level is 3. Here are the descriptions of the 
+different run-levels as they are often implemented:</para>
 
 <literallayout>0: halt the computer
 1: single-user mode
@@ -25,20 +34,20 @@ different runlevels as they are often implemented:</para>
 5: same as 4, it is usually used for GUI login (like X's xdm or KDE's kdm)
 6: reboot the computer</literallayout>
 
-<para>The command used to change runlevels is <command>init
-&lt;runlevel&gt;</command> where &lt;runlevel&gt; is the target runlevel. For
+<para>The command used to change run-levels is <command>init
+&lt;runlevel&gt;</command> where &lt;runlevel&gt; is the target run-level. For
 example, to reboot the computer, a user would issue the <command>init
 6</command> command. The <command>reboot</command> command is just an alias for
 it, as is the <command>halt</command> command an alias for <command>init
 0</command>.</para>
 
 <para>There are a number of directories under <filename>/etc/rc.d</filename>
-that look like like rc?.d where ? is the number of the runlevel and rcsysinit.d
-which contain a number of symbolic links. Some begin with a K, the others begin
+that look like like rc?.d (where ? is the number of the run-level) and rcsysinit.d
+all containing a number of symbolic links. Some begin with a K, the others begin
 with an S, and all of them have two numbers following the initial letter. The K
 means to stop (kill) a service, and the S means to start a service. The numbers
 determine the order in which the scripts are run, from 00 to 99; the lower the
-number the sooner it gets executed. When init switches to another runlevel, the
+number the sooner it gets executed. When init switches to another run-level, the
 appropriate services get killed and others get started.</para>
 
 <para>The real scripts are in /etc/rc.d/init.d. They do all the work, and the
@@ -46,7 +55,7 @@ symlinks all point to them. Killing links and starting links point to
 the same script in /etc/rc.d/init.d. That's because the scripts can be 
 called with different parameters like start, stop, restart, reload, 
 status. When a K link is encountered, the appropriate script is run with 
-the stop argument. When a S link is encountered, the appropriate script 
+the stop argument. When an S link is encountered, the appropriate script 
 is run with the start argument.</para>
 
 <para>There is one exception. Links that start with an S in the
@@ -85,4 +94,3 @@ own LFS system). The files given here are just an example of how it can be
 done in a nice way (well, what we consider nice -- you may hate it).</para>
 
 </sect1>
-