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 647f462affce4bb17cdf1c5d2a9d2cbb99c79085..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>
@@ -229,32 +235,33 @@ is needed only by scripts starting services logging to syslog.</p>
 
 <dl>
 
-<dt>$local_fs          
-<dd>all local file systems are mounted.
+<dt>$local_fs
+<dd>all local file systems are mounted. (In Debian, / and /var/ is available)
 
-<dt>$network           
+<dt>$network
 <dd>basic networking support is available. Example: a server program
-could listen on a socket.
+could listen on a socket. (In Debian, network interfaces are up)
 
-<dt>$portmap           
+<dt>$portmap
 <dd>daemons providing SunRPC/ONCRPC portmapping service as defined in
 RFC 1833: Binding Protocols for ONC RPC Version 2 (if present) are
 running.
 
-<dt>$remote_fs         
-<dd>all remote file systems are available. In some configurations, file
-systems such as /usr may be remote. Many applications that require
-$local_fs will probably also require $remote_fs.
+<dt>$remote_fs
+<dd>all remote file systems are available. In some configurations,
+file systems such as /usr may be remote. Many applications that
+require $local_fs will probably also require $remote_fs. (In Debian,
+/usr/ and NFS directories are guaranteed to be mounted)
 
-<dt>$time              
+<dt>$time
 <dd>the system time has been set, for example by using a network-based
 time program such as ntp or rdate, or via the hardware Real Time
 Clock.
 
-<dt>$syslog            
+<dt>$syslog
 <dd>system logger is operational.
 
-<dt>$named             
+<dt>$named
 <dd>IP name-to-address translation, using the interfaces described in
 this specification, are available to the level the system normally
 provides them. Example: if a DNS query daemon normally provides this