Minor fixes.

[homepage.git] / mypapers / 200802-bootsequence / 200802-bootsequence.html

diff --git a/mypapers/200802-bootsequence/200802-bootsequence.html b/mypapers/200802-bootsequence/200802-bootsequence.html
index 3091fb946dbd5e04de6cb371184b541ea6fdf640..772f7c7b143424cd032fbd95c639b4e5ec2ee0cd 100644 (file)
--- a/mypapers/200802-bootsequence/200802-bootsequence.html
+++ b/mypapers/200802-bootsequence/200802-bootsequence.html
@@ -143,8 +143,12 @@ Getting it right is often hard.
 default be the reverse of the start sequence.  It isn't.
 
 <p>Reordering is hard and require cooperation between maintainers of
-all packages involved.  Given two packages with two scripts inserted
-with the default settings in Debian:
+all packages involved.
+
+<h2>The ordering problem - an example</h2>
+
+<p>Given two packages with two scripts inserted with the default
+settings in Debian:
 
 <p>Package A: script_a sequence 20 (start and stop)
 <br>Package B: script_b sequence 20 (start and stop)
@@ -161,7 +165,7 @@ B and C to get something like this:
 have to change their sequence number too.  Only way to discover this
 is by a lot of testing, or documenting script dependencies.
 
-<h2>A ordering solution</h2>
+<h2>An ordering solution</h2>
 
 <p>Let each script document its dependency, and generate sequence
 numbers using this dependency information.  Example:
@@ -177,7 +181,9 @@ numbers using this dependency information.  Example:
 <br>script_a start seq 3, stop seq 1
 
 <p>An implementation of this system is the dependency based boot
-sequencing, provided in the insserv package.</p>
+sequencing, provided in the insserv package.  Uses format specified in
+Linux Software Base to document dependencies.</p>
+
 
 
 <h2>LSB headers for insserv</h2>