On Tuesday 24 April 2007, Michal Zugec said:
Will Stephenson wrote / napísal(a):
On Friday 20 April 2007 11:54:19 Martin Schmidkunz wrote:
On Thu, 19 Apr 2007 13:51:05 +0200, Will Stephenson
wrote:
What would be nice would be if the admin could add NM settings in YaST and then be clearly be presented with a choice to store these as system settings, default for all users, or apply them to a subset of users - what do you think of that?
Sounds interesting at first :-) What NM settings would that be?
Just the wireless settings that have to be read by NM.
But this is already done in YaST - write configuration for wireless devices. Am I missing something? Or did you mean some additional informations?
I was responding to Francis' assertion that we don't want NM settings in YaST, "because it confuses users", so that my use case is recorded in the design. *) We already do this and need this for the use case I posted last night *) It could be made clearer that YaST sets the system defaults for NetworkManager but that each user can add his/her own networks *) It might be nice (but not very realistic) to be able to also pre-set users' NM settings via YaST - write ~/.kde/share/config/knetworkmanagerrc and the corresponding gconf keys. Additionally *) NM 0.7 will add support for multiple simultaneously active devices, static IP, and proper PPP device control - therefore much like the non-NM settings we have in Yast now. It will obtain the system's config from a dbus settings service running as root, before a user logs in and adds their own settings. The default implementation of this settings service will probably be a stripped-down nm-applet reading gconf. It would be wise to keep this in mind now when redesigning network config so that you don't have to start from scratch next version. Will -- Desktop Engineer Interfaces and Applications Team -- To unsubscribe, e-mail: opensuse-usability+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-usability+help@opensuse.org