Fix errors reported by textproc/igor:

- wrap long line
- use two spaces at sentence start
- use tabs instead of spaces
- space after content
- straggling <tag>

Event:	    vBSDcon FreeBSD Hackathon

en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml

@@ -4,26 +4,38 @@
 
      $FreeBSD$
 -->
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="sysinit">
+<chapter xmlns="http://docbook.org/ns/docbook"
+  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
+  xml:id="sysinit">
   <title>The SYSINIT Framework</title>
 
-  <indexterm><primary>SYSINIT</primary></indexterm>
+  <indexterm>
-  <indexterm><primary>dynamic initialization</primary></indexterm>
+    <primary>SYSINIT</primary>
-  <indexterm><primary>kernel initialization</primary>
+  </indexterm>
-    <secondary>dynamic</secondary></indexterm>
+  <indexterm>
-  <indexterm><primary>kernel modules</primary></indexterm>
+    <primary>dynamic initialization</primary>
-  <indexterm><primary>kernel linker</primary></indexterm>
+  </indexterm>
+  <indexterm>
+    <primary>kernel initialization</primary>
+    <secondary>dynamic</secondary>
+  </indexterm>
+  <indexterm>
+    <primary>kernel modules</primary>
+  </indexterm>
+  <indexterm>
+    <primary>kernel linker</primary>
+  </indexterm>
 
   <para>SYSINIT is the framework for a generic call sort and dispatch
-    mechanism. FreeBSD currently uses it for the dynamic
+    mechanism.  FreeBSD currently uses it for the dynamic
-    initialization of the kernel. SYSINIT allows FreeBSD's kernel
+    initialization of the kernel.  SYSINIT allows FreeBSD's kernel
     subsystems to be reordered, and added, removed, and replaced at
     kernel link time when the kernel or one of its modules is loaded
     without having to edit a statically ordered initialization routing
-    and recompile the kernel. This system also allows kernel modules,
+    and recompile the kernel.  This system also allows kernel modules,
     currently called <firstterm>KLD's</firstterm>, to be separately
     compiled, linked, and initialized at boot time and loaded even
-    later while the system is already running. This is accomplished
+    later while the system is already running.  This is accomplished
     using the <quote>kernel linker</quote> and <quote>linker
     sets</quote>.</para>
 
@@ -32,13 +44,13 @@
 
     <variablelist>
       <varlistentry>
-        <term>Linker Set</term>
+	<term>Linker Set</term>
-        <listitem>
+	<listitem>
-          <para>A linker technique in which the linker gathers
+	  <para>A linker technique in which the linker gathers
-            statically declared data throughout a program's source files
+	    statically declared data throughout a program's source
-            into a single contiguously addressable unit of
+	    files into a single contiguously addressable unit of
-            data.</para>
+	    data.</para>
-        </listitem>
+	</listitem>
       </varlistentry>
     </variablelist>
   </sect1>
@@ -51,24 +63,25 @@
     <para>SYSINIT relies on the ability of the linker to take static
       data declared at multiple locations throughout a program's
       source and group it together as a single contiguous chunk of
-      data. This linker technique is called a <quote>linker
+      data.  This linker technique is called a <quote>linker
-      set</quote>. SYSINIT uses two linker sets to maintain two data
+      set</quote>.  SYSINIT uses two linker sets to maintain two data
       sets containing each consumer's call order, function, and a
       pointer to the data to pass to that function.</para>
 
     <para>SYSINIT uses two priorities when ordering the functions for
       execution.  The first priority is a subsystem ID giving an
-      overall order for SYSINIT's dispatch of functions. Current predeclared
+      overall order for SYSINIT's dispatch of functions.  Current
-      ID's are in <filename>&lt;sys/kernel.h&gt;</filename> in the enum
+      predeclared ID's are in
-      list <literal>sysinit_sub_id</literal>. The second priority used
+      <filename>&lt;sys/kernel.h&gt;</filename> in the enum
-      is an element order within the subsystem. Current predeclared
+      list <literal>sysinit_sub_id</literal>.  The second priority
-      subsystem element orders are in
+      used is an element order within the subsystem.  Current
+      predeclared subsystem element orders are in
       <filename>&lt;sys/kernel.h&gt;</filename> in the enum list
       <literal>sysinit_elem_order</literal>.</para>
 
-  <indexterm><primary>pseudo-devices</primary></indexterm>
+    <indexterm><primary>pseudo-devices</primary></indexterm>
 
-  <para>There are currently two uses for SYSINIT. Function dispatch
+    <para>There are currently two uses for SYSINIT. Function dispatch
       at system startup and kernel module loads, and function dispatch
       at system shutdown and kernel module unload.  Kernel subsystems
       often use system startup SYSINIT's to initialize data
@@ -77,11 +90,11 @@
       Device drivers should avoid using <literal>SYSINIT()</literal>
       directly.  Instead drivers for real devices that are part of a
       bus structure should use <literal>DRIVER_MODULE()</literal> to
-      provide a function that detects the device and, if it is present,
+      provide a function that detects the device and, if it is
-      initializes the device.  It will do a few things specific to
+      present, initializes the device.  It will do a few things
-      devices and then call <literal>SYSINIT()</literal> itself.
+      specific to devices and then call <literal>SYSINIT()</literal>
-      For pseudo-devices, which are not part of a bus structure,
+      itself.  For pseudo-devices, which are not part of a bus
-      use <literal>DEV_MODULE()</literal>.</para>
+      structure, use <literal>DEV_MODULE()</literal>.</para>
   </sect1>
 
 
@@ -92,15 +105,15 @@
       <title>Interface</title>
 
       <sect3>
-        <title>Headers</title>
+	<title>Headers</title>
 
-          <programlisting>&lt;sys/kernel.h&gt;</programlisting>
+	<programlisting>&lt;sys/kernel.h&gt;</programlisting>
       </sect3>
 
       <sect3>
-        <title>Macros</title>
+	<title>Macros</title>
 
-        <programlisting>SYSINIT(uniquifier, subsystem, order, func, ident)
+	<programlisting>SYSINIT(uniquifier, subsystem, order, func, ident)
 SYSUNINIT(uniquifier, subsystem, order, func, ident)</programlisting>
       </sect3>
     </sect2>
@@ -109,14 +122,13 @@ SYSUNINIT(uniquifier, subsystem, order, func, ident)</programlisting>
       <title>Startup</title>
 
       <para>The <literal>SYSINIT()</literal> macro creates the
-        necessary SYSINIT data in SYSINIT's startup data set for
+	necessary SYSINIT data in SYSINIT's startup data set for
-        SYSINIT to sort and dispatch a function at system startup and
+	SYSINIT to sort and dispatch a function at system startup and
-        module load.  <literal>SYSINIT()</literal> takes a uniquifier
+	module load.  <literal>SYSINIT()</literal> takes a uniquifier
-        that SYSINIT uses to identify the particular function dispatch
+	that SYSINIT uses to identify the particular function dispatch
-        data, the subsystem order, the subsystem element order, the
+	data, the subsystem order, the subsystem element order, the
-        function to call, and the data to pass the function. All
+	function to call, and the data to pass the function.  All
-        functions must take a constant pointer argument.
+	functions must take a constant pointer argument.</para>
-        </para>
 
       <example>
 	<title>Example of a <literal>SYSINIT()</literal></title>
@@ -138,9 +150,7 @@ void foo_arg(void *vdata)
         struct foo *foo = (struct foo *)vdata;
         foo_data(foo);
 }
-SYSINIT(bar, SI_SUB_FOO, SI_ORDER_FOO, foo_arg, &amp;foo_voodoo);
+SYSINIT(bar, SI_SUB_FOO, SI_ORDER_FOO, foo_arg, &amp;foo_voodoo);</programlisting></example>
-	</programlisting>
-      </example>
 
       <para>Note that <literal>SI_SUB_FOO</literal> and
 	<literal>SI_ORDER_FOO</literal> need to be in the
@@ -153,7 +163,8 @@ SYSINIT(bar, SI_SUB_FOO, SI_ORDER_FOO, foo_arg, &amp;foo_voodoo);
 	handle tuning kernel parameters.</para>
 
       <example>
-	<title>Example of Adjusting <literal>SYSINIT()</literal> Order</title>
+	<title>Example of Adjusting <literal>SYSINIT()</literal>
+	  Order</title>
 
 	<programlisting>static void
 mptable_register(void *dummy __unused)
@@ -171,8 +182,8 @@ SYSINIT(mptable_register, SI_SUB_TUNABLES - 1, SI_ORDER_FIRST,
       <title>Shutdown</title>
 
       <para>The <literal>SYSUNINIT()</literal> macro behaves similarly
-        to the <literal>SYSINIT()</literal> macro except that it adds
+	to the <literal>SYSINIT()</literal> macro except that it adds
-        the SYSINIT data to SYSINIT's shutdown data set.</para>
+	the SYSINIT data to SYSINIT's shutdown data set.</para>
 
       <example>
 	<title>Example of a <literal>SYSUNINIT()</literal></title>
@@ -192,8 +203,7 @@ struct foo_stack foo_stack = {
 void foo_flush(void *vdata)
 {
 }
-SYSUNINIT(barfoo, SI_SUB_FOO, SI_ORDER_FOO, foo_flush, &amp;foo_stack);
+SYSUNINIT(barfoo, SI_SUB_FOO, SI_ORDER_FOO, foo_flush, &amp;foo_stack);</programlisting>
-	</programlisting>
       </example>
     </sect2>
   </sect1>