![](https://seccdn.libravatar.org/avatar/c85a197ab6892580f11430a464c8ff5e.jpg?s=120&d=mm&r=g)
On Sat, Nov 29, 2014, at 03:01 PM, Jon Nelson wrote:
I have to say, on the laptops which run KDE, using network manager is *great*.
agreed.
It has stabilized and works very well. Not being able to have more than one VPN is a problem, but it's a bit on the esoteric side.
Not so esoteric, it's a frequent use case here. Which is why laptops have always (prior to 13.2/wicked) been config'd to switch between traditional ifup/down control & NM
I'm dismayed to see that systemd-networkd is not available as an alternative, but at least network manager works well enough.
NM can be made to work in some cases, certainly. Admittedly, it's a far better option than wicked currently is -- at least routing isn't flaky (I see similar issues), and tunnels are reliable. That said, NM is not a robust server solution and, at least here, will never be seen production servers. For all the whining about "global death & destruction" wrought by have systemd forced upon us with little alternative, (personally, I find it very useful), this wicked situation is far, far more destructive from our perspective. At least with systemd on opensuse, there was at a release cycle + where the previous alternative, sysVinit remained available and fully functional. Not so with wicked. Or, afaict. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org