On Wednesday, 15 November 2017 14:45 Stefan Seyfried wrote:
But in the "good old days" sysconfig ifcfg-scripts were exactly this: bash scripts. They basically needed ifplugd to do stuff like "cable hotplug detection". Wicked, OTOH is compiled (C or C++?) code which could implement the ifplugd functionality easily in the wicked daemons which are running anyway. Just like NetworkManager is doing since its beginning. Resorting to starting an extra daemon, its code being more than 10 years unmaintained, to handle cable hotplug is an -- how do I write it politely -- ... "strange" design decision.
I fully agree that it would make more sense if wicked did implement the functionality itself. After all, it doesn't run ip or ethtool either and talks to the kernel instead. In my experience, wicked maintainers/developers are reasonable people who can be talked to. (Which is part of why, while I'm still not convinced having wicked as replacement of ifup/ifdown rather than alternative was the right decision, I still trust wicked more than systemd-networkd.) So I believe if you tell them that you are going to get rid of ifplugd and suggest to implement the functionality in wicked, there is a good chance they will agree. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org