I like it.  One comment though:

> b) /etc/init.d/
> 
> 	This contains files - one for each function to execute on
> 	startup - which can either be invoked directly or used to
> 	generate /etc/rc (via mkrc).
> 
> 	Currently there are 75 scripts in /etc/init.d.
> 
> 	NOTE:	During development this directory was called `/etc/rc.d'.
> 		It was changed to `/etc/init.d' because:
> 		    a) prior art (cf. SYSV), and people are used to running
> 			/etc/init.d/foo start
> 		    b) `completion-conflict-with-rc[03].d' asthetics :-)
> 
> 		If there's a strong argument for /etc/rc.d over
> 		/etc/init.d, we could rename it to /etc/rc.d.

Can the scripts in `/etc/init.d' be invoked directly, as in
`/etc/init.d/nfs stop'?  This is not clear as the example scripts do
not seem to be directly executable.

If not, i.e. you need to run some interpreter on them explicitly, I
would not use the `/etc/init.d' name as that will add confusion.

=========================================================================
Eduardo Horvath				eeh@netbsd.org
	"I need to find a pithy new quote." -- me