diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2025-04-28 08:43:57 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska@appnovation.com> | 2025-04-28 08:43:57 +0000 |
| commit | 168d89131415de7590daa00dc5929aeb8727078e (patch) | |
| tree | 79c9cad554e63998bda545965c91caa50f0ba627 /doc/s6-svscan-1.html | |
| parent | 63ae0841dcc024464290edf9080ce536a1d7905e (diff) | |
| download | s6-168d89131415de7590daa00dc5929aeb8727078e.tar.gz | |
Latest batch of fixes
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'doc/s6-svscan-1.html')
| -rw-r--r-- | doc/s6-svscan-1.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/s6-svscan-1.html b/doc/s6-svscan-1.html index c947637..2714d61 100644 --- a/doc/s6-svscan-1.html +++ b/doc/s6-svscan-1.html @@ -117,7 +117,7 @@ before it unmounts the filesystems would be bad.) <p> init does not have the right to die, but fortunately, <em>it has the right -to <a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/execve.html">execve()</a>!</em> +to <a href="https://pubs.opengroup.org/onlinepubs/9799919799/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-4? It only makes sense to have an init process that handles stage 1, then executes into an init process that |
