Brian Masinick
Like some others, I use the default runit because it’s “default”. And because I saw runit was an option in antiX 23 too, so I expected it to be stable “by now”. (However on 23 I didn’t use it yet.)
But I didn’t know the init can make differences like font in PlayOnLinux programs, as mentioned above. Based on that, I made a test to try boot sysV – and wow, my sound is not muted and on value 0, like it is when booting with runit. (I planned to take a look later, for now I can set that once a day.)
(32bits antix26-Full version on Lenovo X61s from 2007. BUT I didn’t know inits can make small differences like these. I know just the basics of it. So whichever you guys like is good for me. If I need to make a start script, I’ll figure out.)
The reasons for those differences can vary: one possibility is that the default configurations for the service managers in the different init alternatives provide different defaults. Another possibility is that we were not completely consistent with our build configurations, but I’m not sure about that point.
In any case, all of this IS configurable, regardless of what you are using. For instance, in the case of fonts, these can also be set in DIFFERENT applications, even if they default to common values. For instance, while the default fonts may be set up the same way in the browsers and the console terminals, applications such as the roxterm console terminal and the Firefox Web Browser each allow you to set the fonts you prefer to use, and they can be completely different fonts between the browser and the console terminal, so these selections are not bound or restricted completely by the init alternative; it merely establishes a default configuration.
I hope this helps. Let us know if you need additional details or just experiment with your Web Browser, file manager or console terminal; they ARE configurable.
--
Brian Masinick
Alternate "Search B":
This search page