[artix-general] [s6] How to migrate from legacy s6-rc-bundle with default+boot bundles to new contents.d

[Colin S]

On 31/01/2022 14:59, Dudemanguy wrote:

>> Is there any way to check no service/oneshot was missed, other than 
>> listing them?  Am I missing something?
> 
> You can list the contents of a bundle with s6-rc-db contents bundle. If
> there's something in the bundle that isn't in the contents.d directory,
> then you know you've still got some services missing. s6-db-reload will
> always spit a warning at you if it picks up some service that was added
> with s6-rc-bundle-update.

What is the situation now, under the new system, with respect to srv/log 
service pairs?

Using sshd just as an example, service directories for sshd-srv and 
sshd-log exist in /etc/s6/sv having been installed by package 
openssh-s6. However my compiled database also contains a bundle called 
sshd with these two as its only contents for which no corresponding 
source directory exists. This bundle would seem to have been generated 
at some point. Was this treated as a special case and the bundle created 
automatically? If so, does this still happen?

When migrating to the new regime, what are the correct entries to make 
in /etc/s6/adminsv/default/contents.d in order to start sshd on boot? 
Would sshd alone work or are both sshd-srv and sshd-log required?

Presumably one could always recreate the existing situation in compiled 
by using a custom sshd bundle in adminsv if that isn't done 
automatically anyway somehow. There are quite a few -s6 packages which 
have a similar structure, so it would be tidier not to have to make 
doubled-up entries for each if that were possible.

Thanks.

Colin