[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#773386: marked as done (release-notes: Systemd related updates to "before reboot" and Recovery proceedures)

Your message dated Sat, 29 Apr 2017 10:31:00 +0000
with message-id <5cb96b64-1404-79e1-b385-b6a872ce8341@thykier.net>
and subject line Re: Bug#773386: release-notes: Systemd related updates to "before reboot" and Recovery proceedures
has caused the Debian Bug report #773386,
regarding release-notes: Systemd related updates to "before reboot" and Recovery proceedures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
773386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773386
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
Severity: normal
Tags: jessie

(X-CC to systemd maintainers for input)

The release notes have a "Prepare for recovery"[1] and "Things
to do before rebooting" section[2].  They currently does not cover any
systemd related preparation.

I believe we should consider covering some/all of:

 * My system does not boot after upgrading to systemd.  How do I figure out
   what the problem is and how do I get a shell/some method to fix it?

 * Is there someone I can do to check for issues after upgrading but before
   rebooting?  Like do we have a tool to report:
   - There are cycles in your init configuration between the following
     services / init.d scripts.
   - You have an old init.d script laying around that is likely to break
     stuff because of reason X
   - etc.


So far, I got following for recovery:

  * (When boot fails) Reboot and alter kernel command line to include
    "systemd.unit=rescue.target".
  * (Before reboot or from rescue shell) Run systemctl enable
    debug-shell.service to get a (passwordless) root shell on TTY9
    "just in case"
  * (Before upgrade) Back up /sbin/init and use it on the kernel cmd line
     as last resort [Presumably Jessie-only]


On the "before reboot", I got nothing so far.  I am hoping you do.

If you got known issues to be documented in the Release Notes (or
other suggestions for improvements), please file additional bugs.
We got some items covered in [3], but I would not be surprised if I
had missed one or some of the existing ones could be improved.

Thanks,
~Niels

[1] https://www.debian.org/releases/jessie/amd64/release-notes/ch-upgrading.en.html#recovery

[2] https://www.debian.org/releases/jessie/amd64/release-notes/ch-upgrading.en.html#nownownow

[3] https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system

(udev/CONFIG_DEVTMPFS): https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.en.html#udev-needs-kernel-with-devtmpfs

--- End Message ---
--- Begin Message --- 
On Tue, 27 Jan 2015 21:37:27 +0100 Niels Thykier <niels@thykier.net> wrote:
> [...]

I believe we got what we needed for the upgrade.  Given nothing else
have materialized on this bug in the past years, I suspect we can close
it now.  Should there be new information, please file a new bug for it.

Thanks,
~Niels

--- End Message ---
Reply to: