summaryrefslogtreecommitdiffstats
path: root/system/s6-linux-init/README
diff options
context:
space:
mode:
Diffstat (limited to 'system/s6-linux-init/README')
-rw-r--r--system/s6-linux-init/README14
1 files changed, 12 insertions, 2 deletions
diff --git a/system/s6-linux-init/README b/system/s6-linux-init/README
index 6f017d3435..1b0669f679 100644
--- a/system/s6-linux-init/README
+++ b/system/s6-linux-init/README
@@ -41,7 +41,15 @@ TMPFS_DIR=/path/to/directory to the script like below:
At some point in boot time, an instance of s6-svscan will become PID 1,
using $TMPFS_DIR/service as its scan directory by default. This can be
altered by passing SCAN_DIR=path/to/directory to the script, changing
-the scan directory to $TMPFS_DIR/path/to/directory.
+the scan directory to $TMPFS_DIR/path/to/directory. For example, if you
+want to change the scan directory to /run/s6/service, you can pass
+SCAN_DIR=s6/service to the script like below:
+
+ SCAN_DIR=s6/service ./s6-linux-init.SlackBuild
+
+Note that we don't use absolute path for SCAN_DIR here, since it is
+relative to $TMPFS_DIR, which defaults to /run (as mentioned
+previously).
Upstream recommends building skarnet.org software with static libraries,
as most of skarnet.org software are small enough that shared libraries
@@ -64,4 +72,6 @@ If you just want to build and use skarnet.org software, building only
the static libraries should be sufficient.
If you want the binaries to be linked against the shared versions of the
-skarnet.org libraries, pass LINK_SHARED=yes to the script.
+skarnet.org libraries, pass LINK_SHARED=yes to the script, i.e.,
+
+ LINK_SHARED=yes ./s6-linux-init.SlackBuild