I have figured this out but I thought I would include what I learned for
those who are also curious about doing a migration. The first step was
walking through and checking the errors that run on startup, for s6 the
output you see on your console during boot is stored in
/run/uncaught_logs/. With the current file in that dir actually
containing text output. Trailing through I found some warning regarding
the /var/log/dmesg file, it seems that when s6 was starting it was
trying to create that as a directory where as normally with something
like openrc, it is a file. Removing the dmesg file seemed to clear that
right up and on the next boot I had my default bundle working. I am not
quite sure of the interaction here that causes this detail to result in
the default bundle not running but I believe it has something to do with
the init system blocking until the catch all logger is started. My guess
is that this has something to do with this comment in the source code:
https://github.com/skarnet/s6-linux-init/blob/master/src/init/s6-linux-init.c#L109
This might be worth mentioning if migration ever gets its own wiki page.
Thanks,
Moody
On 9/5/20 3:41 PM, Jacob Moody via artix-general wrote:
> Hello,
>
> I recently migrated from openrc to s6 with the help of this forum post
> here:
> https://forum.artixlinux.org/index.php/topic,1369.msg9492.html#msg9492.
>
> However upon creating the default bundle it seems to not want to start
> on boot. I have ensured that both the default bundle and the services
> it's calling are in the current database but upon boot it seems to not
> start it. I even tried hacking the rc.init by changing the rl variable
> to default but still can't seem to get it to run on boot. I was
> wondering if anyone here knows if perhaps this forum post skips a step
> or there is some additional configuration that needs to be done.
>
>
> Thanks,
> Moody
More information about the artix-general
mailing list