On 2015-01-15 01:12, Stuart Prescott wrote: > Hi Niels, > > thanks for looking at this -- it's good to have it documented. > > > [...] > > cheers > Stuart > >
Hi Stuart and Hendrik, Thanks for your comments. I believe I have addressed them all in the attached patches, which I have committed to the SVN. Please let me know if you any further remarks or any remarks to the proposed changes. :) Once again, thanks for contributing to the release notes. Thanks, ~Niels
>From 5a6ef207fa6990a74348a63c060b0dcdb13aca9b Mon Sep 17 00:00:00 2001 From: Niels Thykier <ni...@thykier.net> Date: Thu, 15 Jan 2015 08:28:11 +0100 Subject: [PATCH 1/2] en/issues: Extended the modified sysvinit script section Based on feedback from Stuart Prescott and Hendrik Boom. Signed-off-by: Niels Thykier <ni...@thykier.net> --- en/issues.dbk | 25 +++++++++++++++++-------- 1 file changed, 17 insertions(+), 8 deletions(-) diff --git a/en/issues.dbk b/en/issues.dbk index 63b2289..f41620f 100644 --- a/en/issues.dbk +++ b/en/issues.dbk @@ -294,9 +294,10 @@ ProtectSystem=yes </note> <para> If you have modified some of your init scripts provided by Debian, - please be aware that these may now have been replaced by a systemd - unit file. If you have debsums installed, you can check for locally - modified init scripts by using the following shell command. + please be aware that these may now have been superseded by a + systemd unit file or by systemd itself. If you have debsums + installed, you can check for locally modified init scripts by + using the following shell command. </para> <screen> debsums -c -e | grep ^/etc/init.d @@ -311,13 +312,14 @@ debsums -c -e | grep ^/etc/init.d </screen> <para> If either command flags any files and their corresponding packages - now provides an systemd unit file, the systemd unit file will take - precedence to your locally modified init script. Depending on the - nature of the change, there are different way to perform the - migration. + <emphasis>or</emphasis> the <systemitem + role="package">systemd</systemitem> now provides an systemd unit + file for that service, the systemd unit file will take precedence + to your locally modified init script. Depending on the nature of + the change, there are different way to perform the migration. </para> <para> - If needed be, it is possible to override the systemd unit file to + If necessary, it is possible to override the systemd unit file to have it start the sysvinit script. For more information on systemd unit files, please have a look at the following resources. </para> @@ -330,6 +332,13 @@ debsums -c -e | grep ^/etc/init.d </para> </listitem> <listitem> + <para> + <ulink + url="http://0pointer.de/public/systemd-man/systemd.special.html">systemd.special + â Special systemd units</ulink> + </para> + </listitem> + <listitem> <para><ulink url="http://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime/">My Service Can't Get Realtime!</ulink> (also contains a very short -- 2.1.4
>From 7e6b359c97eafc4a7c677bf46642371667dd3678 Mon Sep 17 00:00:00 2001 From: Niels Thykier <ni...@thykier.net> Date: Thu, 15 Jan 2015 08:38:32 +0100 Subject: [PATCH 2/2] Note systemd and LXC in the "special care" section Signed-off-by: Niels Thykier <ni...@thykier.net> --- en/issues.dbk | 2 +- en/upgrading.dbk | 21 +++++++++++++++++++++ 2 files changed, 22 insertions(+), 1 deletion(-) diff --git a/en/issues.dbk b/en/issues.dbk index f41620f..b2522fe 100644 --- a/en/issues.dbk +++ b/en/issues.dbk @@ -367,7 +367,7 @@ debsums -c -e | grep ^/etc/init.d </para> </section> -<section id="issues-lxc"> +<section id="lxc-upgrade-issues"> <!-- Wheezy to Jessie --> <title>Upgrade considerations for LXC hosts and containers</title> diff --git a/en/upgrading.dbk b/en/upgrading.dbk index 13b1a30..d0f0e3a 100644 --- a/en/upgrading.dbk +++ b/en/upgrading.dbk @@ -1099,6 +1099,27 @@ and &releasename;. There are a small number of cases where some intervention may be required, either before or during the upgrade; these are detailed below on a per-package basis. </para> +<section id="issues-systemd"> + <!-- Wheezy to Jessie --> + <title>systemd</title> + <para> + The Debian upgrade from &oldreleasename; to &releasename; + will by default migrate your init system from the SysV to systemd. + Depending on your system and setup, you may need to do some + manual changes. We have detailed known issues in <xref + linkend="systemd-upgrade-default-init-system" />. + </para> +</section> +<section id="issues-lxc"> + <!-- Wheezy to Jessie --> + <title>LXC</title> + <para> + If you have LXC installed, you may need special care when + upgrading your system and your containers. Please have a + look at <xref linkend="lxc-upgrade-issues" /> for known + issues and solutions. + </para> +</section> <section id="issues-sudo"> <title>Sudo</title> -- 2.1.4