From 572dcf1b75b04de5c17e0be249dd6a447b3cda70 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Sat, 1 Nov 2014 18:52:32 +0000 Subject: [PATCH] 762194_automatic_switch_to_systemd: Draft with two options --- 762194_automatic_switch_to_systemd/draft.txt | 29 ++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 762194_automatic_switch_to_systemd/draft.txt diff --git a/762194_automatic_switch_to_systemd/draft.txt b/762194_automatic_switch_to_systemd/draft.txt new file mode 100644 index 0000000..94ab950 --- /dev/null +++ b/762194_automatic_switch_to_systemd/draft.txt @@ -0,0 +1,29 @@ +===== text in version A and also version B ===== + +0. We offer advice and make our views known (Constitution 6.1(5): + +1. The Technical Committee decision in February, selecting systemd as + the default init system for Linux, should not be read as a decision + that existing systems should be automatically switched to systemd. + +===== text in version B only ===== + +2. We are currently sceptical about the idea that existing Debian + GNU/Linux systems should be automatically switched to systemd. + +3. We do not want to prejudge, interfere with, or contradict, the + General Resolution process on init systems which is currently + ongoing. Some of the GR options imply that automatic switching + (both during upgrades, and during leaf package installations) will + be necessary in at least some circumstances. + +4. For the moment, we invite concrete proposals for technical changes + which would arrange that 1. new jessie installations using Linux + would get systemd but 2. existing installations retain their + existing init system so far as possible. + +5. After the result of the General Resolution is known, we intend to + formally resolve the question of automatic switching of init + systems. Our decision on that question will of course be + consistent with the successful General Resolution option, whatever + that may be. -- 2.39.2