Could you please keep width of your text below 72?
[2018-11-13 16:28] alecfeld...@disroot.org > It is quite strange how debian uses /etc/service to store currently > active services. Other distributions use /run/runit or /var/service, > though /run makes more sense. Perhaps /etc/service could be moved > somewhere else? This would solve the issue with etc being read-only. Probably. But such changes with large disruptive potential I'd prefer to make after release. > To be honest, there's a lot about the way runit is packaged on Debian > that should be changed. You are welcome to contribute. But remember -- Debian is all about stability and smooth transition. Changes that require manual intervention on existing installations are not acceptable. > The part about only having a handful of -run packages isn't a h uge > deal. I can make them myself, although creating packages for those > services would be handy. Your help here would be more then welcome. I could grant you access to runit-team, so you could create more -run packages. I will sponsor them. > On an unrelated note, runit uses sysvinit scripts to boot. While this > is fine, if I want to use runit and nothing else, I shouldn't need to > have sysv-rc installed as some sort of backend. This sort of leads to > a wider issue that I'm not sure I should discuss here. Question in not in `sysv-rc', but in `initscripts'. This is issue. But I do not have power to solve it. All scripts in /etc/rcS.d contains mess of hacks, intended to workaround issues with different file systems, kernels, configurations and so on. Sure, I can just copy initscripts into src:runit, but why?
