https://bugzilla.novell.com/show_bug.cgi?id=478110 User kmachalkova@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=478110#c1 Katarina Machalkova changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Network AssignedTo|yast2-maintainers@suse.de |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|jsrain@novell.com |qa@suse.de --- Comment #1 from Katarina Machalkova 2009-02-25 02:29:09 MST --- This is because NetworkManager can no longer read system-wide sysconfig settings used by YaST. These two are now two separate network configuration frontends, independent of each other. YaST cannot read/write NetworkManager settings (thus, displays a warning on startup) and NetworkManager cannot use YaST settings. This is intentional. However, I guess there was no specific FATE id related to this ... Tambet, can you please clarify? (all in all, the initial description is a collection of NetworkManager issues and I don't quite understand why it has been filed under YaST component) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478110 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=478110#c2 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |YaST2 AssignedTo|tambet@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|qa@suse.de |jsrain@novell.com --- Comment #2 from Tambet Ingo 2009-02-25 09:08:02 MST --- If we wanted to support this, then yast will need to grow support for creating NetworkManager network configuration. The reason why it got removed from 11.1 is that it was extremely confusing and only worked in some cases. The network configuration in yast is static and doesn't map well to NM configuration: The connection data in yast is *the* connection, importing it to NM makes it *a* connections. Some specific issues: * A card in yast is set to use specific configuration (any device type, any IP method, ...). Isn't it expected that the system will always use that configuration? NM is dynamic in it's nature and can use any compatible configuration it has. Restricting that dynamic nature of NM makes it useless, it's the reason of having a daemon instead of shell scripts. * A card in yast is set to "activate manually". In NM, it's a per-configuration property, so if you have another matching connection in NM which is marked "connect automatically", the device is activated automatically. * Some "traditional" method configuration data is kept in global files which means there's no difference between configured data and current state. For example, when NM would try to import a yast configuration, it would need to the list of DNS servers configured in yast. But that information is not available anywhere - the current dynamic /etc/resolv.conf might have any values, depending on which devices (and VPN and ...) are active at that specific moment. So in summary, if it's confusing that yast doesn't allow NM configuration, there's no other non-confusing way to fix that, other than make yast module for NM configurations. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=478110 User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=478110#c4 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #4 from Scott Couston 2009-03-03 16:54:29 MST --- Resolved as Fixed in Duplicate indicated *** This bug has been marked as a duplicate of bug 423881 *** https://bugzilla.novell.com/show_bug.cgi?id=423881 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.