On 10/13/18 12:58 PM, Holger Levsen wrote: > On Sat, Oct 13, 2018 at 06:01:43AM +0100, Ben Hutchings wrote: >>> Has policy changed regarding support for multiple inits, or is it just that >>> no one is maintaining the shim and sysvinit-core? >> >> The latter. systemd-shim has been orphaned for over 2 years, and has >> RC bugs. sysvinit currently has two maintainers, but they've only >> ever made one upload (over a year ago). > > It seems that these facts are either largely ignored or unknown and I > wonder if some noise should be made so that interested people can pick > up the work now and not only complain later. I don't think that is only the smaller issue we are facing here. The bigger "problems" for those who do not like systemd will be: - the typical package maintainer won't test initscripts - more and more upstreams are shipping systemd services only and skip init script creation. For my packages I can state that I do not have a single machine which is not using systemd - and to be honest - I won't waste my time in writing/debugging initscripts. If there is one, I'll review it if it looks sane and then maybe ship it. And I'm saying "maybe" here, as for new packages, I will NOT shit it as active init script because I will only put stuff in my packages I have tested well enough. After using a lot of systemd now I will never go back to init scripts. Systemd comes with a steep learning curve, but one you've stated using its features you'll never go back. -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Attachment:
signature.asc
Description: OpenPGP digital signature