I believe it was decided to move to networkd first and then switch
resolvconfs - https://blueprints.launchpad.net/ubuntu/+spec/core-1505
-networkd-vs-ifupdown.
I vaguely recall that was due to systemd-resolvconf not being able to
work with an ifup/down based networking setup.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453167
Title:
replace resolvconf with systemd-resolvd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1453167/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
