Needs systemd unit or sysv init script
Bug #1351316 reported by
Martin Pitt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| friendly-recovery (Ubuntu) |
Fix Released
|
Low
|
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.
| description: | updated |
| Changed in friendly-recovery (Ubuntu): | |
| status: | Triaged → In Progress |
| assignee: | nobody → Martin Pitt (pitti) |
| Changed in friendly-recovery (Ubuntu): | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in friendly-recovery (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package friendly-recovery - 0.2.26
---------------
friendly-recovery (0.2.26) utopic; urgency=medium
* Drop /usr/share/
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-
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 local-fs-
emergency.
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