This variable nominates the "upper" filesystem for an overlay mount.
This will be accessed read-write and it constitutes the "private"
files of the subhost.
-
++
If UPPER is different from LOWER, then the root file system is set up
as an overlay mount. In that case WORK (below) must be defined as a
directory outside of but on the same mount as UPPER.
-
++
If UPPER is the same as LOWER, then the subhost root filesystem is not
setup as an overla. Rather it is set up as a bind mount, if UPPER is
different from LIVE, or just as a pre-mounted LIVE filesystem.
This variable tells which services should be started on the
overlay-boot startup. The default value is +networking ssh+.
-
++
Note that if no services are started, then +overlay-init+ starts a
+dummy_service+ so as to keep +/.reaper+ from running out of child
processes, as it otherwise will exit and thereby terminate
This variable nominates the "upper" filesystem for an overlay mount.
This will be accessed read-write and it constitutes the "private"
files of the subhost.
-
++
If UPPER is different from LOWER, then the root file system is set up
as an overlay mount. In that case WORK (below) must be defined as a
directory outside of but on the same mount as UPPER.
-
++
If UPPER is the same as LOWER, then the subhost root filesystem is not
setup as an overla. Rather it is set up as a bind mount, if UPPER is
different from LIVE, or just as a pre-mounted LIVE filesystem.
This variable tells which services should be started on the
overlay-boot startup. The default value is +networking ssh+.
-
++
Note that if no services are started, then +overlay-init+ starts a
+dummy_service+ so as to keep +/.reaper+ from running out of child
processes, as it otherwise will exit and thereby terminate