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
 <a href="//skarnet.org/software/s6-portable-utils/s6-ln.html">s6-ln</a>
 utility is recommended, because the
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/ln.html">ln</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ln.html">ln</a>
 standard actually <em>forbids</em> an atomic replacement, so utilities that
 follow it to the letter, for instance, <tt>ln</tt> 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. </li>
 
 <p>
  s6-rc is free software. It is available under the
-<a href="http://opensource.org/licenses/ISC">ISC license</a>.
+<a href="https://opensource.org/licenses/ISC">ISC license</a>.
 </p>
 
 <h3> Download </h3>
@@ -138,9 +138,9 @@ the previous versions of s6-rc and the current one. </li>
 <h3> Similar work </h3>
 
 <ul>
- <li> <a href="http://jjacky.com/anopa/">anopa</a> is another service manager
+ <li> <a href="https://jjacky.com/anopa/">anopa</a> is another service manager
 for s6, with a similar design (but no compilation phase). </li>
- <li> <a href="http://homepage.ntlworld.com/jonathan.deboynepollard/Softwares/nosh.html">nosh</a>
+ <li> <a href="https://jdebp.eu/Softwares/nosh/">nosh</a>
 is a complete init system and service manager for Unix. </li>
 </ul>
 
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.
 
 <p>
  Unlike other service managers such as
-<a href="http://jjacky.com/anopa/">anopa</a>, s6-rc separates the
+<a href="https://jjacky.com/anopa/">anopa</a>, 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 <a href="s6-rc.html">s6-rc</a> again with the
 proper arguments. This is more powerful than the old
-<a href="http://www.tldp.org/LDP/sag/html/run-levels-intro.html">runlevels</a>:
+<a href="https://www.tldp.org/LDP/sag/html/run-levels-intro.html">runlevels</a>:
 it is possible to change the live state to <em>any</em> 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. </li>
  The <tt>examples/source</tt> 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
-<a href="http://busybox.net/">busybox</a> and the
+<a href="https://busybox.net/">busybox</a> and the
 <a href="//skarnet.org/software/">skarnet.org</a> 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 @@
 <a href="//skarnet.org/software/s6/">s6</a>,
 <a href="http://smarden.org/runit/">runit</a>,
 <a href="http://b0llix.net/perp/">perp</a> or
-<a href="http://cr.yp.to/daemontools.html">daemontools</a>
+<a href="https://cr.yp.to/daemontools.html">daemontools</a>
 define a <em>service</em> 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:
 </p>
 
 <ul>
- <li> <a href="http://savannah.nongnu.org/projects/sysvinit">sysvinit</a>,
+ <li> <a href="https://savannah.nongnu.org/projects/sysvinit">sysvinit</a>,
 the historical GNU/Linux init system, and its companion set of
 <tt>/etc/rc.d</tt> init scripts that some distributions like to
 call <tt>sysv-rc</tt>. Note that sysvinit <em>does</em> have
@@ -174,14 +174,15 @@ a joke.
 </p>
 
 <ul>
- <li> <a href="http://upstart.ubuntu.com/">Upstart</a> was the first
-one. On the front page, in the "feature highlights" section:
-"Tasks and Services are started and stopped
-by events. Events are generated as tasks and services are started
-and stopped." Do you understand what that means? I don't. Also,
-Upstart was the first system that used <tt>ptrace</tt> on the
-processes it spawned in order to keep track of their forks. If
-you don't know what that means: it was pure insanity. </li>
+ <li> <a href="https://upstart.ubuntu.com/">Upstart</a> was the first
+one. The <em>concepts</em> in Upstart are actually pretty good: in
+theory, it's a decent event-based service manager. Unfortunately, the
+<em>implementation</em> is less than ideal. For instance, the service
+file format is full of adhocisms breaking the principle of least surprise.
+But most importantly, Upstart was the first system that used <tt>ptrace</tt>
+on the processes it spawned in order to keep track of their forks. If
+you don't know what that means: it's complete insanity, using a debug
+feature in prodution, with heavy impact on security and efficiency. </li>
  <li> <a href="https://en.wikipedia.org/wiki/Launchd">launchd</a>,
 Darwin's init and service manager. The wikipedia page (linked here
 because Apple doesn't see fit to provide a documentation page for
@@ -192,7 +193,7 @@ has to link in a XML parsing library, and it communicates with process 1
 via a Mach-specific IPC mechanism. Is this the sleek, elegant
 design that Apple is usually known for? Stick to selling iPhones,
 guys. </li>
- <li> <a href="http://www.freedesktop.org/wiki/Software/systemd/">systemd</a>,
+ <li> <a href="https://www.freedesktop.org/wiki/Software/systemd/">systemd</a>,
 the main protagonist (or antagonist) in the "init wars". It has the same
 problems as launchd, up by an order of magnitude;
 <a href="//skarnet.org/software/systemd.html">here is why</a>.