Ken Moffat wrote: > On Mon, Nov 25, 2013 at 07:44:16PM -0500, Alan Feuerbacher wrote: >> >> Apparently things in the linux world have changed recently with respect >> to naming devices generally, so that old conventions like "eth0" have >> been replaced by conventions that are said to make more sense. I suppose >> "enp3s0" makes sense to some people, but "eth0" makes more sense to a >> non-expert like me. >> > > If you don't want to run Lennart-from-scratch, this is what I use > to get back to a sane name - > > # fix the ecpXsY ethernet naming > echo "# dummy, so that network is once again on eth0" > >/etc/udev/rules.d/80-net-name-slot.rules > > Strictly, just creating an empty file with that name will solve the > problem - but empty files are fragile and their meaning is likely to > be forgotten! This fixes the major abomination since udev was merged > into systemd - that undesirable change is now also in eudev and > Bruce's udev-from-systemd. > > I leave it to the people drinking Lennart's kool-aid to explain why > names such as enp3s0 are saner than eth0!
I know the answer to that one. To ensure that really big iron with many ethernet devices will not have ethx assigned in random order due to race conditions. It probably comes up more frequently when using systemd which launches processes during boot up in parallel. In other words, a solution for the 1% that need it forced on the 99% who don't. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
