A workaround is to create an empty file /etc/modprobe.d/systemd.conf but this is too imprecise. The files that systemd uses should ideally be named specifically for their purpose so that they can be overridden without affecting any future changes in systemd, e.g. /etc/modprobe.d/systemd-dummy.conf and /etc/modprobe.d/systemd- bonding.conf
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937953 Title: systemd forcibly disables use of dummy/bond interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937953/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
