Hello,
I have some questions.
Background: I've only read the documentation so far, I haven't installed
s6-frontend or the newest s6-rc yet, I have experience using s6-linux-init
and previous versions of s6-rc as init system components on Gentoo.
1) Stores: 's6 repository init' and 's6 repository sync' create a
"reference database" using s6-rc-compile, with the union of services
defined in all stores linked in the repository, correct? That means that
all stores must present a coherent view of services; they can't be
uncoordinated, or otherwise s6-rc-compile could fail while trying to make
the reference database, right? So, how is usage of two or more stores
envisioned? s6-frontend's documentation mentions a scenario in which one of
them is managed by the package manager of the distribution; what would
additional stores (if any) be expected to contain?
2) Sets and prescriptions: so, an s6-rc compiled database made from a set
that has no masked services would be equivalent to the reference database,
plus one automatically added bundle (the one that 's6 system boot' starts)?
3) Set inconsistencies I: if service A's prescription is "active", A
depends on service B, and B's prescription is "usable", does 's6 set check'
report that as an inconsistency? If service A's prescription is "usable", A
depends on service B, and B's prescription is "active", does 's6 set check'
report that as an inconsistency?
4) Set inconsistencies II: does 's6 set commit' fail if the commited set
has unfixed inconsistencies?
Thanks,
G.
Received on Fri Feb 06 2026 - 03:40:24 CET