How Debian managed the systemd transition [LWN.net]

How Debian managed the systemd transition

Posted Sep 18, 2015 16:42 UTC (Fri) by HenrikH (subscriber, #31152)
In reply to: How Debian managed the systemd transition by dlang
Parent article: How Debian managed the systemd transition

Actually the current pinning seams to be a much better solution that creating a dev with the mac as name. Just as long as one rembers to edit /etc/udev/rules.d/70-persistent-net.rules if one have changed the NIC. Now with enx00249b0e398f one would possible have to edit tons and tons of config files if unlucky.

to post comments

How Debian managed the systemd transition

Posted Sep 19, 2015 18:08 UTC (Sat) by cortana (subscriber, #24596) [Link] (2 responses)

The problem with the old 'pinning' approach was that it was racey. I have had to recover servers that stopped working because the interface usually known as eth0 is now called eth1_rename, and there is another interface now called eth0, or some such.

How Debian managed the systemd transition

Posted Sep 20, 2015 0:04 UTC (Sun) by dlang (guest, #313) [Link] (1 responses)

Interesting, i never ran into that.

It may be that I got bit by the rename due to card changes and disabled it entirely before the odds caught up with me.

How Debian managed the systemd transition

Posted Sep 20, 2015 13:14 UTC (Sun) by cortana (subscriber, #24596) [Link]

It is a probabilistic problem; you might never see it in your whole career; or you might see it twice in a week. It is annoying when those who have never seen it happen to them (and I am not including you in this set) assume that it is not a problem, and rubbish the efforts of those who are trying to fix it properly by removing the underlying race condition.