lp://qastaging/ubuntu/utopic-proposed/friendly-recovery
- Get this branch:
- bzr branch lp://qastaging/ubuntu/utopic-proposed/friendly-recovery
Branch merges
Branch information
Recent revisions
- 32. By Martin Pitt
-
* 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 local-fs-pre.target. This is based on
emergency.target, but watches out for "recovery" on the kernel command
line, similar to upstart. (LP: #1351316) Add alternative "systemd-sysv"
dependency (LP: #1351306) - 30. By Stéphane Graber
-
[ James Hunt ]
* README: Fixed typo.
* lib/recovery-mode/options/ system- symmary: added brief LVM and APT
summaries.[ Stéphane Graber ]
* Update upstart job to ensure /run/shm and /run/lock are present. - 29. By Stéphane Graber
-
* Fix failsafeX (thanks to James Hunt)
* Add new system-summary script, trying to give some useful information
about the system
* Add 'apt-get autoremove' to the clean script
* Update translations - 28. By Stéphane Graber
-
* Upload the right version of recovery-menu
(previous upload was a debug version ...)
* Better handle the fsck case by having it be a one-time option that
can only be triggered from read-only mode. - 27. By Stéphane Graber
-
* Rework of the menu
- All options are now displayed again.
- Filesystem state (read-only or read/write) is displayed in the title.
- User is prompted the first time they access an option requiring
read/write access to the filesystem.
- netroot option was dropped and replaced by a new network option
that tries to configure the network by calling ifupdown,
Network Manager and falling back to regular dhclient.
- A warning is now shown when the user wants to resume the boot
sequence warning them that some X drivers don't work when the
system was booted without KMS. Recommending the user to reboot in
that case. - 26. By Stéphane Graber
-
Replace remaining call to basename (/usr/bin/basename) by a bashism.
To avoid using anything from /usr in friendly-recovery. - 25. By Stéphane Graber
-
* Update upstart job
- Make sure to deal with anything failing (upstarts run with set -e)
* Update l10n.sh
- If /usr/share/locale doesn't exist, define eval_gettext as a simple
echo and return. - 24. By Stéphane Graber
-
* Update upstart job
- Drop all the || null in pre-start and replace by a final exit 0
- Start setvtrgb from pre-start
- Emit mounted MOUNTPOINT=/run from pre-start (to start resolvconf)
- Start udev from pre-start
- Manually call udevadm trigger/settle from pre-start (upstart job hangs)
- Turn off kernel output before showing the menu to avoid screen corruption - 23. By James Hunt
-
debian/
friendly- recovery. upstart: Add missing emits stanzas
to avoid breaking 'initctl check-config' (LP: #888095).
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://qastaging/ubuntu/vivid/friendly-recovery