Quoting Steve Litt (sl...@troubleshooters.com): > Also, while I have your attention, all you guys talk about two > different packages: runit and runit-init.
Upstream distinction, not distro. runit-init is a binary executable that can be the first process. Or, if you prefer, you can use your choice of other, different init process. There's also supervisor code in the form of programs 'sv' and 'runsv', plus some other stuff. (Disclaimer: I've only skim-read a bunch of Web-page coverage.) A distro package based on upstream _might_ furnish everything. If I can make a general comment: You are starting to encounter the complex bits of designing and maintaining distro policies, including the bits you and Adam separately have mentioned. All points made are well with noting, including yours about wondering how to best ensure that Devuan users opting for one init system package can smoothly change to a different one. This is where you and the Project will need to work out and document policy, and then collectively make sure it's followed. Fixing file/directory namespace collisions is just the start of that. _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
