Hey Laurent,
I am suggesting something like a [ -t ${TARGETDIR} ] option for the
s6-linux-init program.
s6-linux-init shall then copy the run-image hierarchy to ${TARGETDIR}
and run s6-svscan on ${TARGETDIR}/service.
My rationale is as follows:
The policy for s6 and s6-rc I am working on will, on most if not all
desktop setups, feature a "user supervision-tree" (a leaf of the "system
supervision-tree")
and a "graphical supervision-tree" (started from whatever graphical shell the
user runs (e.g. a wayland compositor)).
To organize these properly I plan to use the following directory
structure under /run, with ${NAME} being the name of my policy.
${TARGETDIR} would be "/run/${NAME}/system" in this case:
/run
|
+- ${NAME}
+- system
| + service
| + s6-rc
| + uncaught-logs
|
+- user
+- ${USER1}
| +- user
| | +- service
| | +- s6-rc
| |
| +- graphical
| +- service
| +- s6-rc
|
+- ${USER2}
+- user
| +- service
| +- s6-rc
|
+- graphical
+- service
+- s6-rc
And so on for more users.
I am currently using a simpler, scripted init,
but I would like to provide a s6-linux-init config
to allow users of my policy to have the more fancy features of s6-linux-init
like the LSB-3.0.0 shutdown interface conformance and similar.
Regards,
Paul
signature.asc
Description: PGP signature
