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
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1453167
Title:
replace resolvconf with systemd-resolvd
Status in ubuntu-meta package in Ubuntu:
Confirmed
Bug description:
For the sake of smoother user experience and easier learning curve
would be nice to get rid of legacy resolvconf package and use systemd-
resolvd which is nicely integrated with the rest of the stack and uses
unified configuration file systax and conventions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1453167/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
