Context

You might have seen this post series from my organization related setting up Pipewire and Hyprland on Devuan. Another potentially important piece of the puzzle is my earlier post related to asking about the possibility of switching to the Devuan OpenRC Setup Post-Desktop Live Install.

Essentially, at the time I created the guide, I was memed into using the default OpenRC configuration offered on some of the .iso installation options for Devuan. I'm new to init freedom altogether, so I'm playing around with what init system would be optimal and friction-least for a computer user. For an unrelated reason, my installation borked after an attempt at cleaning up unnecessary packages on my system (the exact cause to me is a mystery). This post, after reading a little bit about how Devuan approaches init ("enhanced" SysVInit being apparently more performant, and how the default OpenRC apparently uses SysVInit for certain things anyway), is about exploring as another "branch" of experimentation of how this can cleanly be done using Devuan's default init system.

What is happening?

Essentially, when I boot up into the tty on the SysVInit computer, I'm getting logs similar but not limited to:

startpar: service(s) refused failure: x11-common ... failed!
startpar: service(s) refused failure: pulseaudio-enable-autospawn cups cups-browsed ... failed!

I'm not sure how to exactly extract the logs that pop on a tty on startup, upon learning how, I'll edit/add a post to include them.

My assumption would be that this would essentially be a game of whack-a-mole of telling SysVInit scripts to not call certain applications to allow applications to function properly. For example, in the first snippet above, I'm curious if having pulseaudio-enable-autospawn fail would cause me problems later in regard to being able to use printers with cups. Conversely, I'm curious if this could not be the case and it is simply a matter of flipping off configuration files or hiding the messages in come way in the case that, generally speaking, the ... Failed! messages are inconsequential (an example being that pulseaudio-enable-autospawn failing doesn't appear to be affecting my ability to use audio devices with Pipewire).

Any pointers appreciated.

Best,