On 10/04/18 19:46, Richard Brown wrote:
Hi All,
In both Leap & Tumbleweed we currently have the following logic for choosing which tool manages your network after installation
"IF laptop AND NetworkManager is being installed THEN use NetworkManager, ELSE wicked"
I've noticed an increasing trend that this can lead to confusion.
Many users from other distributions expect NetworkManager on their desktops regardless of whether they are using a laptop or a desktop.
GNOME expects NetworkManager by default and shows a rather unpleasant error when loading up the settings screen without it.[1]
There are certainly classes of hardware where NetworkManager might be wanted that will never match "IF laptop" - eg. my personal Inter Compute Stick.
And "IF laptop" is dependant on YaST correctly detecting you're using a laptop, which isn't 100% accurate, so occasionally even laptops might end up with wicked unexpectedly.
I would like to propose a possible solution.
It looks like we should be able to pin the choice of network tool to specific system role.
I would like to propose that the installation options KDE and GNOME therefore always have NetworkManager by default
Server & Transactional will always have wicked by default
Custom will keep the current "autodetect" behaviour, because we cant be sure that the environment that the user is installing has support for NetworkManager in this case.
Whatever is setup "by default" during installation will be able to be changed in YAST after the installation, just like it is today.
What do we all think? If there is strong support for this idea I think Ludwig is prepared to let me try and slip it in as a late feature for Leap 15, so please let your opinions be heard loudly and quickly either way.
Regards,
Richard
I have also thought about something like this in the past as it makes more sense for all of enlightenment to default to network manager as well, rather then just basing it on a role would it be possible to have a "Network Manager Default" package then we could do it on a pattern or package basis rather then per role, I'd much rather a solution that can fix the issue properly for everything. A downside to that is if not done right it could lead to people being magically swapped from one to the other on tumbleweed which we may not want. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org