From e4821d7a10ee2096b689a66baa9b974d51339bc3 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Tue, 23 May 2017 11:05:54 +0000 Subject: Switch doc to schemeless URLs --- doc/faq.html | 20 +++++++-------- doc/index.html | 16 ++++++------ doc/overview.html | 20 +++++++-------- doc/s6-rc-bundle.html | 10 ++++---- doc/s6-rc-compile.html | 28 ++++++++++----------- doc/s6-rc-db.html | 6 ++--- doc/s6-rc-dryrun.html | 6 ++--- doc/s6-rc-fdholder-filler.html | 14 +++++------ doc/s6-rc-init.html | 14 +++++------ doc/s6-rc-oneshot-run.html | 6 ++--- doc/s6-rc-update.html | 10 ++++---- doc/s6-rc.html | 12 ++++----- doc/upgrade.html | 56 +++++++++++++++++++++--------------------- doc/why.html | 24 +++++++++--------- 14 files changed, 121 insertions(+), 121 deletions(-) (limited to 'doc') diff --git a/doc/faq.html b/doc/faq.html index 09c3a99..bfb995b 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -6,14 +6,14 @@ s6-rc: FAQ - +

s6-rc
-Software
-skarnet.org +Software
+skarnet.org

s6-rc: Frequently Asked Questions

@@ -93,7 +93,7 @@ file. Using the filesystem as a key-value store is a good technique to avoid parsing, and skarnet.org packages do it everywhere: for instance, -s6-envdir +s6-envdir uses the file name as a key and the file contents as a value. The s6-rc-compile source format is just another instance of this technique. @@ -196,7 +196,7 @@ time you compile a service database, you could run:
  • When you compile a new service database, always compile it to a unique name, preferrably in the same directory as your current compiled database. You can for instance use a TAI64N timestamp, obtained by -s6-clock, +s6-clock, to create such a name: 
      stamp=`s6-clock`
@@ -218,14 +218,14 @@ new database will be used on the next boot, atomically update the link:
  s6-ln -nsf compiled-$stamp /etc/s6-rc/compiled
    The use of the -s6-ln +s6-ln utility is recommended, because the ln standard actually forbids an atomic replacement, so utilities that follow it to the letter, for instance, ln from GNU coreutils, cannot be atomic: they first remove the old link, then create the new one. If you do not have -s6-ln, +s6-ln, you need to perform an unintuitive workaround to get POSIX-compliant tools to do the right thing: ln -sf compiled-$stamp /etc/s6-rc/compiled/compiled && @@ -284,7 +284,7 @@ using OpenRC
    • You can now run compile your s6-rc service database, and use the s6-rc engine as your service manager. Transitions will use your original init scripts, and the supervision -features of s6 will +features of s6 will not be used, but you will get proper dependency tracking and easy state changes.

    @@ -321,7 +321,7 @@ bundle that contains nothing at all!

    In your boot script (/etc/rc.init, for instance, if you're using -s6-linux-init), +s6-linux-init), after invoking s6-rc-init, just ask s6-rc to start the set of services you want up @@ -416,7 +416,7 @@ addressed by Unix distributions.

    - Like the rest of skarnet.org + Like the rest of skarnet.org software, s6-rc aims to provide mechanism, not policy: it is OS-agnostic and distribution-agnostic. Providing boot scripts, or anything of this kind, would go against this principle; it is diff --git a/doc/index.html b/doc/index.html index e4132c5..c83d0f3 100644 --- a/doc/index.html +++ b/doc/index.html @@ -6,13 +6,13 @@ s6-rc - a service manager for s6 - +

    -Software
    -skarnet.org +Software
    +skarnet.org

    s6-rc

    @@ -21,7 +21,7 @@

    s6-rc is a service manager for -s6-based +s6-based systems, i.e. a suite of programs that can start and stop services, both long-running daemons and one-time initialization scripts, in the proper order according to a @@ -47,11 +47,11 @@ scripts are also run in a controlled environment.

    @@ -125,7 +125,7 @@ the previous versions of s6-rc and the current one.

    Similar work

    diff --git a/doc/overview.html b/doc/overview.html index 12d5e4d..c585cbb 100644 --- a/doc/overview.html +++ b/doc/overview.html @@ -6,14 +6,14 @@ s6-rc: an overview - +

    s6-rc
    -Software
    -skarnet.org +Software
    +skarnet.org

    An overview of s6-rc

    @@ -59,11 +59,11 @@ around while the filesystem is mounted.