There are plenty of examples, some of them bespoke 3rd party things. An equally large issue though are legacy technicians who aren't familiar with systemd's way of doing things yet (I've been trying to get them up to speed though).
But the crux is if returning to ifupdown is offered as an option, then it needs to work as expected. If there's more to reverting to the old way than merely 'apt install ifupdown' then the documentation and config file comments referring to this needs to be updated to outline these steps. If a sysadmin disables systemd-networkd, it should stay disabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771236 Title: forced use of systemd-networkd interferes with ifupdown in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
