❦ 11 mai 2013 22:08 CEST, Josselin Mouette <joss@debian.org> :
>> I can't agree with having no choice with regard to init. We aren't
>> all using GNOME, and Debian is used in an extremely diverse set of
>> fields for a multitude of different purposes. No one init is
>> appropriate for all of these applications. systemd fails on safety
>> grounds alone for a good number of uses. That much complexity is
>> an unacceptable risk for PID1 failure.
>
> This is utter bullshit and you should already know it. Systemd is much
> more reliable as a whole than any other implementation. I have yet to
> see a use case where it is not better.
Unfortunately, its current implementation in Debian has some serious
drawbacks:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669101
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697962
Don't get me wrong: I would love to have systemd as a default init. It
would solve many problems and bugs like above would be fixed because the
burden would not rely on systemd maintainers alone (and I suspect the
bugs are here because systemd has to integrate with the current SysV
init).
I only point the current problems with systemd as an example as what we
get with the current situation: inability to fully use systemd.
One year ago, there was a good plan for this:
1. Switch to systemd as default init (or Upstart).
2. Provide a conversion system from (more descriptive) systemd unit
files to some other still supported systems (like the old SysV) with
the ability to override the conversion by shipping an init.d
file. There was a GSoC for this. I remember that the code is here
but there was no followup.
Switching to a default modern init has two benefits:
1. The benefits from the modern init system alone.
2. A proper integration into Debian by removing old cruft from
packages making the new init work as intended by upstream (and
therefore less buggy) and move the responsability of a working init
system to other packages (nobody would blame sysvinit package for a
problem in some init.d files, it should be the same for systemd).
The conversion mechanism is a compromise solution for those that want
freedom of choice on the init system.
Unfortunately, switching to systemd unit files is a requirement for the
whole thing to work and it implies that we switch to systemd by default
and it is a project choice. So, no way to get forward here until we get
a consensus.
--
Program defensively.
- The Elements of Programming Style (Kernighan & Plauger)
Attachment:
pgpSj6lhnFhx6.pgp
Description: PGP signature