On 11.04.2018 09:29, Michal Kubecek wrote:
And... why exactly? So far the only argument you presented (except for strong words like "abomination") was "it's SUSE-only". Should we drop YaST, based on the same logic? Or zypper?
YaST, I would not care too much. Zypper? Probably not. But if all (maybe just all RPM based) distribution would agree on one package management tool, then that would certainly be an improvement. But for wicked. Well, I was at the openSUSE conference in Prague when it was presented, and it was a typical "we invent something before looking left and right what's already there" thing. Actually I still can remember Olaf's puzzled face when the RedHat developers (there was not only openSUSE conf but some other conferences at the same time at the same venue, and so other distro developers were present) asked "why didn't you work with us to get this into the upcoming systemd-networkd?" and he had to admit that he never looked if there are other projects that do the same. Reminded me of the Old (Y2K) SUSE style of bad NIH syndrome. The best thing systemd has brought us IMVHO is, that now all distributions are handled more or less the same from a systems administrator point of view. If distributions mess things up, you can fix them easily with systemd unit dropins most of the time. At work, it does not really matter anymore if people want RHEL7 or SLES12 from me, it's just handled the same way. That's a big plus. Everyone working on sytemd-networkd instead of its own niche implementation would be almost certainly an improvement for everyone. Alternatively, getting everyone else to adopt and work on wicked would also be an option. But given the history of wicked and the design decisions (XML config files...), I doubt that will ever happen.
You don't even know if systemd-networkd can actually do everything we use wicked for but you are absolutely sure switching to it would be an improvement?
I'm fighting wicked every day. I'm quite sure almost everything would be an improvement ;-) At home I even use NetworkManager on servers, because it works better for me (with fixed ifcfg-file configuration) than wicked. Even SUSE Enterprise Products (SOC for example) avoid wicked whenever they can, it seems. But it's getting offtopic here. Executive summary: I support the default of NetworkManager by default for openSUSE. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org