Bug#771825: release-notes: Update information on non-systemd Jessie upgrades and installations

[Svante Signell <svante.signell@gmail.com>]

On Sun, 2014-12-14 at 11:46 +0100, Joost van Baal-Ilić wrote:
> Hi Svante,
> 
> Care to update the patch now that the CTTE-decision has been taken?  I can
> apply the patch today.

> 
> Thanks for your work! Bye,

Attached is an updated patch, adding some information about apt-get
upgrade and apt-get dist-upgrade, as well as the grub new entry. I'll
create a Wheezy image and try out the examples in the patch (if/when
time permits). Maybe somebody else is interested in helping out too?

Thanks!

Index: en/issues.dbk
===================================================================
--- en/issues.dbk	(revision 10513)
+++ en/issues.dbk	(working copy)
@@ -178,12 +178,15 @@
   <para>
     Jessie ships with <systemitem
     role="package">systemd-sysv</systemitem> as
-    <emphasis>default</emphasis> init system.  If you have a
-    preference for another init such as <systemitem
+    <emphasis>default</emphasis> init system.
+    This package is now installed automatically on upgrades.
+  </para>
+  <para>
+    If you have a preference for another init such as <systemitem
     role="package">sysvinit-core</systemitem> or <systemitem
     role="package">upstart</systemitem>, it is recommended to setup
     APT pinning prior to the upgrade.  As an example, to prevent
-    <systemitem role="package">systemd</systemitem> from being
+    <systemitem role="package">systemd-sysv</systemitem> from being
     installed during the upgrade, you can create a file called
     <filename>/etc/apt/preferences.d/local-pin-init</filename> with
     the following contents:
@@ -193,6 +196,11 @@
 Pin: release o=Debian
 Pin-Priority: -1
   </screen>
+  <para>
+    Please note that the upgrade may install packages containing
+    "systemd" in their name even with APT pinning.  These alone do
+    <emphasis>not</emphasis> change your init system.
+  </para>
   <caution>
     <para>
       Be advised that some packages may have degraded behaviour or
@@ -199,14 +207,51 @@
       may be lacking features under a non-default init system.
     </para>
   </caution>
+  <itemizedlist>
+  <listitem>
   <para>
-    Please note that the upgrade may install packages containing
-    "systemd" in their name even with APT pinning.  These alone do
-    <emphasis>not</emphasis> change your init system.  To use
-    systemd as your init system, the <systemitem
-    role="package">systemd-sysv</systemitem> package must be
-    installed first.
+    It is also a good idea to install
+    <systemitem role="package"> sysvinit-core, sysvint and sysvinit-utils
+    </systemitem> as the first packages when upgrading.
+  </para> </listitem>
+  <listitem> <para> apt-get upgrade from Wheezy to Jessie can boot
+  with init=/lib/sysvinit/init unless/until the old sysvinit package
+  is removed by e.g. autoclean.
+  <caution>
+  Don't autoclean until you have installed sysvinit-core if you
+  don't want systemd-sysv installed!
+  </caution>
+  </para> </listitem>
+  <listitem> <para> apt-get dist-upgrade Wheezy to Jessie will get
+  systemd-sysv installed, and sysvinit will be history!! Otherwise
+  you need to install sysvinit-core on next reboot (if your system
+  boots).
+  <caution>
+  Don't dist-upgrade until you have installed sysvinit-core if you
+  don't want systemd-sysv installed!
+  </caution>
+ </para> </listitem>
+  <listitem> <para> grub will get a new menu entry to boot with
+  init=/lib/sysvinit/init if something goes wrong with the switch to
+  systemd-sysv (unless you dist-upgrade). If you are using some other
+  bootloader, e.g. LILO you are on your own. </para> </listitem>
+  <listitem> <para>
+    If you have a desktop environment installed, it is also
+    recommended to install <systemitem
+    role="package">systemd-shim</systemitem> to
   </para>
+  <itemizedlist>
+  <listitem> <para>
+      assist apt and/or aptitude with the upgrade,
+  </para> </listitem>
+  <listitem> <para> avoid getting <systemitem
+  role="package">systemd-sysv</systemitem> installed by mistake,
+  e.g. if you have forgotten to create the pinning file.  </para>
+  </listitem>
+  </itemizedlist>
+  </listitem>
+  </itemizedlist>
+
 <section id="systemd-auto-mounts-incompat">
   <!-- Wheezy to Jessie -->
   <title>Stricter handling of failing mounts during boot under systemd</title>