I've gone through the install three times now over the past two weeks. I have Void Linux on another drive so I'm familiar with the way runit looks when loading the system and how it operates in relation to interacting with services. The first time I loaded Devuan I chose SysV init because it had been such a long time since seeing it last. I have noticed runit is much faster on my machine than SysV, so I chose to reload and at the end I chose runit as the init system. The first time doing this I noticed at startup things didn't look quite right and calling services to either restart or get a status things weren't working. Searching for the location of the service scripts revealed they were in /etc/init.d/ and not where runit would keep them - /etc/sv. So, I reloaded again today just in case I did something wrong the last time. At the end of the install I chose runit as the init system.

When the system rebooted I noticed the same startup behavior. What I've got is a mashup on runit and sysv init. This is acutely annoying.

Is there a special trick to actually getting a discrete runit init system or is the choice at the end of the install just window dressing? I much prefer runit over SysV init.

Thanks in advance...,

Mark