commit 933499e92811080f9725e46765081f25549c390e
parent 6b194d0b07f3f6362d7fb0c96981483301278a41
Author: Gerrit Pape <pape@smarden.org>
Date: Thu, 27 Dec 2001 09:51:19 +0000
runscripts.html linked.
Diffstat:
2 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/doc/index.html b/doc/index.html
@@ -12,6 +12,8 @@
<a href="replaceinit.html">How to replace init</a><br>
<a href="usedietlibc.html">How to use dietlibc</a>
<p>
+<a href="runscripts.html">A collection of run scripts</a>
+<p>
<a href="runit.8.html">The <tt>runit</tt> program</a><br>
<a href="runit-init.8.html">The <tt>runit-init</tt> program</a><br>
<a href="svwaitdown.8.html">The <tt>svwaitdown</tt> program</a><br>
diff --git a/doc/replaceinit.html b/doc/replaceinit.html
@@ -65,10 +65,11 @@ of your boot loader on how to pass <tt>init=/sbin/runit-init</tt> to the
kernel.
<h3>Step 5: Service migration</h3>
The goal is to migrate all services from <i>sysvinit</i> scheme to the
-<a href="http://cr.yp.to/daemontools.html">daemontools</a> design. This
-can be done smoothly. For those services that are not migrated to use
-<tt>run</tt> scripts yet, add the corresponding <tt>init</tt>-script
-startup to <tt>/etc/runit/1</tt>, e.g.:
+<a href="http://cr.yp.to/daemontools.html">daemontools</a> design; take a
+look at these <a href="runscripts.html">run scripts</a> for popular
+services. The migration can be done smoothly. For those services that are
+not migrated to use <tt>run</tt> scripts yet, add the corresponding
+<tt>init</tt>-script startup to <tt>/etc/runit/1</tt>, e.g.:
<pre>
#!/bin/sh
# one time tasks