Re: Systemd predictive network interface names for Stretch
Le 07/06/2017 à 09:16, kuLa a écrit :
> On 2017-06-06 16:56:25, Zach Marano wrote:
>> Sounds good to me too- I haven't come to any other conclusions that will sanely
>> work by default without introducing more complexity in instance initialization
>> logic (whether that is part of cloud-init or otherwise). I was hoping we had a
>> better solution via systemd-networkd.
>
> I personally didn't use systemd-networkd yet so can't tell if it'd be better or
> not, but I am sure trying to enabled this by default in the Official Debian
> image will cause lots of useless discussion and possible another flame war,
> which I prefer to avoid.
>
> So, I'd say right now we have solution which works and hopefully won't cause too
> much friction with in the project, so lets use it.
>
Looking at the examples from
https://wiki.archlinux.org/index.php/systemd-networkd#Configuration_examples
I don't see how systemd-networkd can help solve the problem of devices
naming anyway.
systemd-networkd uses the name that udev provide, so changing the device
order on the pci bus would cause the same problems as with ifudown.
Reply to: