From c86f75f7ca6ea42d7a992f0871e6bd069dd522df Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sun, 4 Oct 2020 17:18:57 +0000 Subject: doc: fix URLs --- doc/faq.html | 2 +- doc/index.html | 6 +++--- doc/overview.html | 4 ++-- doc/s6-rc-compile.html | 2 +- doc/why.html | 23 ++++++++++++----------- 5 files changed, 19 insertions(+), 18 deletions(-) diff --git a/doc/faq.html b/doc/faq.html index d1df02e..17ba7c5 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -220,7 +220,7 @@ new database will be used on the next boot, atomically update the link: The use of the s6-ln utility is recommended, because the -ln +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 diff --git a/doc/index.html b/doc/index.html index d3cac1e..08cad57 100644 --- a/doc/index.html +++ b/doc/index.html @@ -60,7 +60,7 @@ requirement if you link against the shared version of the skalibs library.

s6-rc is free software. It is available under the -ISC license. +ISC license.

Download

@@ -138,9 +138,9 @@ the previous versions of s6-rc and the current one.

Similar work

diff --git a/doc/overview.html b/doc/overview.html index af62e68..9b375cf 100644 --- a/doc/overview.html +++ b/doc/overview.html @@ -103,7 +103,7 @@ A bundle, however, cannot have dependencies.

Unlike other service managers such as -anopa, s6-rc separates the +anopa, s6-rc separates the work of analyzing a set of service definitions, resolving dependencies, and so on, from the work of actually applying the dependency graph to perform live state changes. The former is @@ -180,7 +180,7 @@ script can actually be really short: an invocation of The administrator can make changes to the live state of the machine by manually calling s6-rc again with the proper arguments. This is more powerful than the old -runlevels: +runlevels: it is possible to change the live state to any set of services, not only predefined ones. The only thing that s6-rc will not allow is a state that would break service dependencies; it diff --git a/doc/s6-rc-compile.html b/doc/s6-rc-compile.html index 048f6cb..c00ced8 100644 --- a/doc/s6-rc-compile.html +++ b/doc/s6-rc-compile.html @@ -401,7 +401,7 @@ command. The examples/source subdirectory of the s6-rc package contains a set of service definition directories, which is actually a working, valid set for a Linux system running -busybox and the +busybox and the skarnet.org packages; of course, only the service definition set has been kept, and private information has been removed, so it won't work out-of-the-box without the proper specific files, diff --git a/doc/why.html b/doc/why.html index ccef157..b737c89 100644 --- a/doc/why.html +++ b/doc/why.html @@ -25,7 +25,7 @@ s6, runit, perp or -daemontools +daemontools define a service as a long-lived process, a.k.a daemon. They provide tools to run the daemon in a reproducible way in a controlled environment and keep it alive if it dies; @@ -110,7 +110,7 @@ that still favor simplicity. Among them, for instance: