-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all,
I respect both sides of the discussion, because: a) I once set up an old P3-700 with 5+1 eth cards in 6 different networks as (bridging)router and truly benefited from the ability to change a broken NIC - which happened quite often due scrap-metal hardware - without ending up with martian packages, dhcp service on the wrong places. But that was 1 incident in 10 years. b) I use multi-nic servers, some with onboard and extention NICs c) I tend to move my setups (esp. my laptop) around between different hardware (nearly identical thinkpad R61/X61), and I _share_ my installation with other/new users by cloning my disc (well rsync), lets call this stageN installation. d) I abuse an old multiport GBit card as GBit switch in my desktop, besides an onboard one. e) Some distro/driver constellations (archlinux?) tend to name their wireless lan eth*. This resulted in one decision per setup, whether or not to set /etc/conf.d/udev's > persistent_net_disable="yes" persistent_cd_disable="yes" Either to avoid random names due hardware replacement (a) or changed module loading order (b, inside debian initrd) or to just use kernel names (eth0, wlan0) because no other cards present (c) or the NIC drivers compiled into the kernel (d). e) never happened to me. It always bugged me to fix/reboot systems which needlessly end up with eth1/wlan1 because some stupid pre-persistent_net_disable did not recognize beeing run on an entirely different hardware. So can we just watch out for the disable="yes" setting and migrate it during udev's pkg_install phases __and__ post an big fat warning (elog, news item) on the wall? I assume most linux users do not operate servers/multi-nic/multi-networking setups, do not clone their setups to other hardware. Given that, these user will almost only see the 'my nics changed names and i cannot connect to the internet' errors due some moronic or unavoidable change in initrd/module loading. That might be the driving force behind udev persistence in the first place. I'd be glad if I we respect setups w/ custom-built kernels, w/o initrds, roots capable of choosing network-name-persistence iff needed, users adoring the possibility of just dd(1)'ing installations to new hardware without reinstalling or entering an new product code. rant=1; And I'd like to avoid dozends of conversations like "Yeah, your setup/firewall/rouing/... command no longer works, eth0 is no enp0xx2_at_home_lid_open or was it _bluetooth_turned_off. Didn't you read the post on some derps mailing list." with haunted people not knowing better than asking me about their problems. Not to mention all online documentation/forum posts referring to eth0. rant=0; Keep up the good work! Michael - -- Michael Weber Gentoo Developer web: https://xmw.de/ mailto: Michael Weber <x...@gentoo.org> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlD1FmAACgkQknrdDGLu8JA68wD/Vuw8mL7O0T398QR7OetqDoLN pQ7kJz9nveemDxw7o9MBAJSsyQ/DWIKLsqudXjlXhTPQEd0Od6vDBEL6IeFtXCjc =AfSI -----END PGP SIGNATURE-----
