On 01/17/2014 12:19 PM, Olaf Hering wrote:
On Fri, Jan 17, Robert Schweikert wrote:
But rather than specifying the interface name in the configuration I want wicked to pick the interface for me.
Isnt the fix for your case the use of the tool which used to write 70-persistent-net.rules?
No, because within a kiwi image build we do not want to fiddle with the system stuff. Network setup is still configuration and up to the user. Previously this was easy the user of kiwi would drop etc/sysconfig/network/ifcfg-eth0 into the image via the overlay tree and would have the configuration they want on any target system. That no longer works. In most cases the person building the image will not know if the interface is enp5s0, or has some other name. Thus a "any-name" policy will address this problem and wicked already has it :)
Just something simple as assigning every occouring MAC to eth0 (there will ever be just a single one per boot, right?) and continue to write ifcfg-eth0 as you like.
This is not a wicked problem as wicked just reads existing ifcfg-* files.
Yes it is not a wicked problem. I am try to use wicked as a way/tool to solve the problem introduced with the new device naming scheme in udev for network devices. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: wicked-devel+unsubscribe@opensuse.org To contact the owner, e-mail: wicked-devel+owner@opensuse.org