[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#727708: tech-ctte: Decide which init system to default to in Debian.

On Wed, 6 Nov 2013, Gergely Nagy wrote:

> Please no. That's a maintenance nightmare. I'm fine with one on
> GNU/Linux, another everywhere else (but I'll treat everything else as
> secondary), but supporting all of them, everywhere they're available, is
> madness.


> Freedom of choice remains even when there's a default. We have a default
> desktop, default syslogd, default MTA, default-this, default-that, yet,
> we have alternatives for all of those. We have a default init now, and
> alternatives to that too.
> If we choose a different default, the alternatives can still co-exist,
> like they do now. Freedom is not lost.

Do you read what you write? These two blocks are the inverse of
each other. Either you support them all or they cannot coëxist.

[ vendor lock-in ]
> And change is bad, because...? I'm not sure about you, but I prefer to

Experience shows that vendor lock-in is always bad, because it
prevents you from exchanging one bad component with another.
The fact that things are OSS doesn’t change this, either,
especially as it still leads to massive effort.

> improve my systems instead of holding them hostage to ancient
> technologies, just because there's only one implementation of a
> particular solution.

This is contrary too… you want to switch to one “more modern”
init system, just because it’s the only one that offers you
the features you now think you want, holding you hostage to
whatever technology Poettering thinks nice right now (consider
his track report of abandoning things, too) and preventing
you from using something else instead. (Or something more
suited to a particular job.)

> Switching to systemd/upstart/OpenRC will not mean the rest will be
> dropped.

But that’s just the thing: you said above: one on GNU/Linux,
one on the others, period. This in effect means that all other
systems will be dropped because you don’t want to support
them (unless we keep sysvinit as lowest common denominator,
require maintainers to write init scripts (which can be very
short with a helper, as recent Planet Debian posts showed),
and use the other init systems in compat mode; but the propo-
nents of systemd, upstart *and* openrc (to a lesser amount)
alike *all* want to *not* keep supporting init scripts).

15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)

Reply to: