summaryrefslogtreecommitdiff
path: root/doc/s6-svscan-1.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/s6-svscan-1.html')
-rw-r--r--doc/s6-svscan-1.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/s6-svscan-1.html b/doc/s6-svscan-1.html
index 441e996..a57e199 100644
--- a/doc/s6-svscan-1.html
+++ b/doc/s6-svscan-1.html
@@ -93,7 +93,7 @@ stages and delegating every stage's work to a different script that is
<p>
One init to rule them all?
-<a href="http://en.wikipedia.org/wiki/Porgy_and_Bess">It ain't necessarily so!</a>
+<a href="https://en.wikipedia.org/wiki/Porgy_and_Bess">It ain't necessarily so!</a>
</p>
<a name="stage2">
@@ -102,7 +102,7 @@ stages and delegating every stage's work to a different script that is
<p>
init does not have the right to die, but fortunately, <em>it has the right
-to <a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/execve.html">execve()</a>!</em>
+to <a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/execve.html">execve()</a>!</em>
During stage 2, why use precious RAM, or at best, swap space, to store data
that are only relevant to stages 1 or 3? It only makes sense to have an
init process that handles stage 1, then executes into an init process that