>f) /sbin/mkrc
>
>	Depending upon the options, mkrc generates /etc/rc, /etc/rc.shutdown,
>	/etc/rc0.d and /etc/rc3.d from /etc/init.d/*.
>
>	The generated /etc/rc{,.shutdown} is rather readable sh script
>	(especially for machine generated scripts!)
>
>	/etc/rc0.d will contain symlinks from KxxFOO -> ../init.d/FOO.
>	/etc/rc3.d will contain symlinks from SxxFOO -> ../init.d/FOO.

(snip)

>Implementation timeframe
>========================
>Once I've tested this stuff a bit more, parts of this start appearing
>in the standard distribution. The existing /etc/rc scripts won't be
>modified (except for /etc/netstart; but the functionality should
>remain).
>After that, /etc/rc could be replaced by the output of /sbin/mkrc. 
>Feedback
>========
>Thoughts/comments?

	correct me if I misunderstand something.

	dependency list in /etc/init.d/foo looks good to me at a first glance,
	but when i've done reading it i'm a bit worried about problem tracking
	issues and support issues.
	it will become harder to track problems in rc script as rc script
	will be tailor-made to the installation site.  if random user says
	that she has some problem with start up script, we basically have
	to get her script, read it through, to track the problem.

	since there's little manpower to handle PRs, I would vote to stick
	with simple-and-static rc and rc.conf...

itojun