From 4eddab8f47a77411dd9128bf8307c7b2f6e62a44 Mon Sep 17 00:00:00 2001 From: Don Armstrong <don@donarmstrong.com> Date: Wed, 10 Dec 2014 11:06:13 -0800 Subject: [PATCH] add initial draft for an affirmative ctte decision as discussed --- .../draft_dla.txt | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 762194_automatic_switch_to_systemd/draft_dla.txt diff --git a/762194_automatic_switch_to_systemd/draft_dla.txt b/762194_automatic_switch_to_systemd/draft_dla.txt new file mode 100644 index 0000000..fd745b3 --- /dev/null +++ b/762194_automatic_switch_to_systemd/draft_dla.txt @@ -0,0 +1,37 @@ +In #762194, the Technical Committee was asked to use its power under +§6.1.4 to override the decision of the init package maintainers to +depend on systemd-sysv as the first alternative dependency, thus +ensuring 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 <87mwc9gfsw.fsf@xoog.err.no>[1], 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. + +==OPTION A== + +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. + +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 non-standard inittab + configurations which are unsupported in systemd. + + c) Providing documentation on how to opt to remain with sysvinit on + both initial installs and upgrades. + + d) Numerous bug reports and fixes by contributors who have tested + the systemd migration in their configurations. + + + +1: https://lists.debian.org/87mwc9gfsw.fsf@xoog.err.no -- 2.39.5