On Wed, 02 Nov 2022 21:19:40 +0100 Lorenzo Puliti <plore...@disroot.org> wrote: > Package: runit > Version: 2.1.2-50 > Severity: important > > Partially related to #1022837. > run_sysv_scripts is invoked in stage 1 to run boot scripts > (initscripts); however it skip the sysv script when a runit service > with the same name exists. This is wrong for early boot tasks and it > can break the boot sequence. For example one can have a /etc/sv/udev > longrun that will replace the sysv instance in stage 2, but still > need to run /etc/init.d/udev during eraly boot. >
Thinking more about this, adapting the run_sysv_scripts interface for this will just add further complication and raise the risk of error for a critical phase of boot process. I think reverting to a plain for loop is the most reasonable thing to do; I'm still not sure if it's worth to add a way to mask scripts by name (as suggested in #1022837): the only reasonable use case that I can think of is when a user wants to run late boot scripts as native runit service (oneshots).
