Here is better evidence. Just now I ran the experiment using same kernel version, 4.19.42, as in the xenial experiment reported above.
My conclusions are unchanged. The newly-introduced incompatible and inconsistent behavior depends on the modprobe release, not on the kernel release. I knew this to be true, as stated previously, but now we have clearer evidence on the record. ** Attachment added: "bionic: (same kernel) insmod and modprobe behave differently" https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+attachment/5265060/+files/dummy-beaver.logg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828749 Title: ifconfig dummy0 : Device not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1828749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
