https://bugzilla.novell.com/show_bug.cgi?id=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c9 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|rmilasan@suse.com | --- Comment #9 from Robert Milasan <rmilasan@suse.com> 2013-10-25 08:22:48 UTC --- If Xen has an issue with this new names that means is Xen the problem. Naming a network device weirdly doesn't mean is broken, means Xen is. There should be some support in YaST for naming the network more 'acceptable' for the user, just not sure exactly how. Haven't tried it. Adding the persistent rules can be done easily, but there is always the issue who comes first. Meaning do we use by default Predictable Names or Persistent Names. I'm going with Predictable Names even if they look weird, at least they are supported upstream and work well. -- 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.