27 Feb
2014
27 Feb
'14
10:07 p.m.
On Thu, Feb 27, 2014 at 10:11 PM, Leonid Isaev <lisaev@umail.iu.edu> wrote:
Even better, if networkd exposes a lot of its functionality, netctl could potentially drop the dependency on iproute2 (not that there is a problem with iproute2).
Yes, static things like bridge, bond, and vlan for which netctl profiles are essentially identical to .net{dev,work} files. I think that the only advantage of netctl over networkd in this case is the ability to specify dependencies (via Before= and After=) between the respective units.
So networkd should sort out all that internally, but please let me know if you notice a usecase we are not covering. Cheers, Tom