Correct, purging resolvconf is only supported "out of the box"/"just
works" in 17.10 and up, as resolvconf/libnss-resolve there have the
correct maintainer scripts to do the tansition.
I do not recommend using systemd-resolve in xenial, as it does not have
a stub resolver available, and software that does not use nss will not
be able to have any network resolution without bypassing resolved. Using
systemd-resolved without resolvconf is currently only best supported on
17.10+.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Summary changed:
- systemd-resolved.service
+ systemd-resolved.service doesn't play nice if resolvconf is removed on
xenial, works on artful+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735296
Title:
systemd-resolved.service doesn't play nice if resolvconf is removed on
xenial, works on artful+
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1735296/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
