Removing conflicts of init system
Dmitry Bogatov
KAction at debian.org
Sun Dec 23 14:58:20 GMT 2018
[2018-12-21 23:57] Thorsten Glaser <t.glaser at tarent.de>
> On Fri, 21 Dec 2018, Dmitry Bogatov wrote:
>
> > I propose to replace current approach with update-alternatives(1)
> […]
> > Opinions?
>
> No. update-alternatives is too fragile to handle things like
> /bin/sh and init(8).
What do you mean fragile? Mind to point me to corresponding bug,
maybe update-alternatives system could be improved?
> Also, what Josh Triplett said.
>
> The packages you cited are basically just the hooks to select
> the default init system, most of them is in other, coïnstallable,
> packages already.
No. Only systemd-sysv is what you say. Both sysvinit-core and runit-init
provide actual binaries.
Sure, it is possible to move real content out of `sysvinit-core' and
`runit-init' and replace it with symlinks, but why it is better then
alternatives?
More information about the Pkg-systemd-maintainers
mailing list