On Fri, 06 Feb 2026 11:59:12 +0000
"Laurent Bercot" <ska-supervision_at_skarnet.org> wrote:
> >Unfortunately, I tried to reboot without rebuilding mdevd and got a
> >invalid fd error (04). I'll work on that but will I also have to redo
> >s6-linux-init etc?
>
> It is difficult to help you without knowledge of the circumstances
> of your setup and the exact error messages you're getting. I don't
> know what "04" means here.
>
> Generally speaking, when software gets a major upgrade (for skaware
> that means when the *second* version number changes), as is the case
> with lots of my packages last month, it is best to rebuild everything
> cleanly, because major upgrade means possible compatibility break.
>
> For s6-linux-init, you should rebuild it, but in this precise case,
> despite the latest version being a major bump over the previous one,
> you don't need to run s6-linux-init-maker again.
>
> --
> Laurent
>
Hi Laurent,
I have rebuilt skalibs,execline,s6,s6-rc,sc-linux-init and mdevd
without problems. I have not re-run s6-linux-init-maker.
The kernel loads, I can login and get an 'early agetty' but none of the
compiled service scripts load.
/run/uncaught-logs/current contains one line
s6-rc-init: fatal: unable to open /etc/s6-rc/compiled/current
There is no such file, the current compiled services are in
/etc/s6-rc/compiled linked to /etc/s6-rc/compiled-08-02-26
If s6-rc-init is trying to open "compiled" how do I tell it where it is?
Sorry for the noise; I am obviously out of my depth with this but I did
have two almost identical s6 boot systems running for the last 6 months
but I seem to have broken something in this update.
Ian
Received on Sun Feb 08 2026 - 03:27:01 CET