This bug was fixed in the package friendly-recovery - 0.2.38
---------------
friendly-recovery (0.2.38) unstable; urgency=medium
* Make friendly-recovery block the systemd emergency / rescue shell
modes. LP: #1662137
* Bump debhelper and starndards version, drop dh-systemd build-dep.
* Support activating networking using systemd units for resolved,
networkd, NetworkManager, ifupdown. LP: #1682637
-- Dimitri John Ledkov <x...@ubuntu.com> Thu, 29 Mar 2018 14:38:38
+0100
** Changed in: friendly-recovery (Ubuntu Bionic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to /etc/resolv.conf
not being present
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
