Brian Masinick
I think the multi-init was too ambitious for the available resources/timing — now that it’s out, I say treat it like the RC it might’ve been in a different universe where anti et al had unlimited time (but with the testing known since release).
If the init updates need to happen (probably do as it has been a heavy lift) AND there are not means/volunteers to get booting status coverage, then maybe some grand notice to remaster between updates (?) can be prominently recommended.
I’m in the worst possible hardware setup (laptop) right now, but, if it helps, I can help test in vbox if its worth anything. Just need get definitions of baseline configs to use/retain and objectives.
FWIW.
From what I remember reading, though the final image contains five distinct init alternatives, I believe that the recommendation for the “average user” was to continue using either runit or sysVinit and I believe the default boot setup starts runit. Also we have a tool that can optionally remove other init alternatives, plus set or change the default boot choice.
Personally I have enjoyed using the various alternatives and I frequently use each one. Today I went back to my live USB image and retested several things and had no issues or changes. For me both the live and installed instances of this release not only are satisfactory, the majority of features work without problems and the few quirks are not intrusive or disruptive at all in my day to day usage of any of them.
--
Brian Masinick
Alternate "Search B":
This search page