Comment # 9 on bug 1165366 from Daniel Molkentin

(In reply to Marius Tomaschewski from comment #8)
> (In reply to Daniel Molkentin from comment #7)
> > Wicked maintainers: Does wicked create the ifcfg- files, or just read from
> > them as legacy source of information? If so, any guidance on how the code
> > should work to determine a DHCP vs static IP boot?
> 
> Wicked never creates any ifcfg files or another kind of interface
> configuration.
> This is done by yast2-network or the user.

Ok, as expected

> case $BOOTPROTO in
>   static)
>      printf 'ip=%s:static ' ${ifname}
>      ;;
>   *dhcp*)
>      printf 'ip=%s:%s ' ${ifname} ${bootproto}
>      ;;
>   esac
> 
> There is a BOOTPROTO=6to4 artifact which is basically also BOOTPROTO=static.

I just realized that this is actually caused by a patch from Thomas
(9cc1b76087c3ff17609a28f2142c2c62cd6cc97b) which is now also part of 050. I
didn't realize it at the time but we created a circular dependency between the
nfs and the network-legacy module this way.

This will break for the network-manager module and for the upcoming
network-wicked one. Honestly: I think the network storage modules has no
business setting up the network (i.e. it was wrong before, but not bad, because
there was only one network backend). 

However, the reverse might be true, e.g. for iBPF, the network module needs to
know a bit about the storage part and set things up. The only thing I think we
_should_ do is ensure that the network module (and hence one of its backends)
is loaded. That is already happening in depends().