Needs systemd unit or sysv init script

Bug #1351316 reported by Martin Pitt on 2014-08-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
friendly-recovery (Ubuntu)
Martin Pitt

Bug Description

friendly-recovery only provides an upstart job. It needs an equivalent SysV init.d script or systemd unit so that it works under systemd, too.

Also, the menu needs to be fixed to use the systemd equivalent of "mountall" for mounting r/w.

Martin Pitt (pitti) on 2014-08-04
description: updated
Changed in friendly-recovery (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Martin Pitt (pitti)
Martin Pitt (pitti) on 2014-08-04
Changed in friendly-recovery (Ubuntu):
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package friendly-recovery - 0.2.26

friendly-recovery (0.2.26) utopic; urgency=medium

  * Drop /usr/share/recovery-mode symlink and transition, this happened in
    oneiric already.
  * Move from cdbs to dh to simplify/modernize build system.
  * Update to copyright format 1.0.
  * Bump Standards-Version to 3.9.5.
  * lib/recovery-mode/options/dpkg: Fix ubuntu-release-upgrader mode again:
    Update to Python 3, and fix --datadir.
  * When running under systemd, call its "remount-fs" service for remounting
    r/w instead of mountall.
  * Add systemd unit, hooking into This is based on, but watches out for "recovery" on the kernel command
    line, similar to upstart. (LP: #1351316) Add alternative "systemd-sysv"
    dependency (LP: #1351306)
 -- Martin Pitt <email address hidden> Mon, 04 Aug 2014 12:42:25 +0200

Changed in friendly-recovery (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers