Brian Masinick
You’re most welcome Brian.
By the way, many thanks for your comments on dinit, that I read elsewhere on this forum in a thread about members’ init preferences. Your positive comments encouraged me to try it on the Asus (my oldest/slowest machine) and I have to say I prefer it over runit. The most significant difference, compared to runit, is that it is very much faster to boot and shutdown. It appears to run well with all my usual day-to-day apps, though I haven’t done any printing with it yet. Hopefully that works efficiently too.Cheers, have a good day 🙂
Yeah, dinit has been a REALLY pleasant surprise! I’ve been using it on occasion since February 2024 when our friend @ProwlerGr first joined our forum and presented the idea of “init-diversity” to us then. @CalciumSodium, @ProwlerGr, and a few others that I don’t immediately recall without referencing our thread from TWO YEARS ago set out to experiment with this stuff.
Though the solution was just a “proof of concept” at the time, it had great promise, and I liked dinit even back then. It turns out that out of the many alternatives to systemd, dinit is one of the newest ones. The “66” service manager that works with s6 is also relatively new, enough so that there are no GUI-based tools that I’m aware of to work with the 66 services other than the tool that was added to the Control Centre – that’s probably an “opportunity” for additional work in the future, but back to dinit – wow, just between January and our release in March the development team did a REALLY good job implementing services for each of the init alternatives. The result is that the original init – sysVinit – while it STILL works great after all these years, it doesn’t really have a fancy GUI either, though it does have an easy to use check box menu to select or deselect the desired services. I suppose you could call it “GUI” if we put a graphical menu box around it, but I call that a native screen-based tool.
Dinit, on the other hand, now has a way to enable and disable services right from our own implementation of these services and I noticed the improvement earlier THIS year, after I’d tried this one more than two years ago, but you’re right; it’s neck and neck with runit. I hasten to add, however, that we have ALSO greatly improved our runit services, which are now actually all running completely in runit, whereas for the past 5-6 years we’ve actually been running many (most/all) of the service creation elements from sysVinit, so it wasn’t a true, 100% runit service, whereas in antiX 26, it’s now as far as I can tell a completely runit based group of services that complement the runit process initiation, so both runit and dinit have benefited from this work!
Again we have @ProwlerGr to thank along with @anticapitalista and the other members of the development team for their outstanding implementation of these services. While we did learn a LOT by looking at the work being done in other distributions, in the end, the final results in OUR OWN distribution take the BEST work from other efforts, add our own integration and configuration efforts to it, resulting in what I believe is the finest multi-init effort in the greater Linux ecosystem!
I may be biased, but if there are any efforts that offer five or more init alternatives weaved as smoothly into another distribution, I’d love to see it! I still don’t think it’d be possible to be more lean and efficient than ours is, even if there IS another such effort out there!
--
Brian Masinick
Alternate "Search B":
This search page