Debian Technical Committee: Transition plan to systemd by default
[Posted February 25, 2015 by ris]
| From: |
| Don Armstrong <don-AT-debian.org> |
| To: |
| debian-devel-announce-AT-lists.debian.org |
| Subject: |
| [CTTE #762194] Transition plan to systemd by default |
| Date: |
| Sun, 22 Feb 2015 11:15:32 -0800 |
| Message-ID: |
| <20150222191532.GM6383@teltox.donarmstrong.com> |
In #762194, the Technical Committee was asked to consider the
transition plan of the init package maintainers to have both new
installs and upgrades use systemd by default.
1. The CTTE determined in #727708 that systemd should be the default
init system in Debian.
2. In https://lists.debian.org/87mwc9gfsw.fsf@xoog.err.no, the
maintainers of the init package announced their transition plan for
migrating to systemd as the default init system on both installs
and new upgrades.
3. The init package (and other related packages) currently in jessie
implement this transition.
==== RESOLUTION ====
Using its power under ยง6.1.5 to make statements:
3. The CTTE affirms the decision of the init system package
maintainers to transition to systemd by default on upgrades and to
install systemd by default on new installs.
4. The CTTE appreciates the effort of Debian contributors to mitigate
any issues with the transition by:
a) Providing a fallback boot entry for sysvinit when systemd is the
default init in grub (#757298)
b) Developing a mechanism to warn on inittab configurations which
are unsupported in systemd. (#761063)
c) Providing documentation on how to remain with sysvinit on
upgrades and switch to sysvinit upon installation.
d) Numerous bug reports and fixes by contributors who have tested
the systemd migration in their configurations.
5. The CTTE advises (without overriding any Debian contributor,
maintainer, or team) that any such mitigations should be included
in jessie, to ensure a smooth transition for Debian users.
==== END OF RESOLUTION ====
The committe would like to thank everyone who participated in the
discussion of #762194.
Please see http://bugs.debian.org/762194 for discussion of
this bug.