On 15 November 2015 at 14:03, Richard Melville <[email protected]> wrote: > On 8 November 2015 at 20:37, William Harrington <[email protected]> wrote: >> On Fri, 6 Nov 2015 16:16:03 -0500 >> David Mehler <[email protected]> wrote: >> >>> This next one goes with the network interface. I'd prefer my >>> interfaces to be named eth0, eth1, etc and to let Linux worry about >>> the driver needed, I like consistent interface names. >>> >>> [ 3.930679] e1000 0000:02:01.0 eno16777736: renamed from eth0 >>> [ 3.938555] udevd[2664]: renamed network interface eth0 to eno16777736 >>> >>> There was a section in the book on this, which I have done, this is is >>> indicating I missed something. Any ideas welcome. >>> >>> Thanks a lot. >>> Dave. >> >> Some more information: >> http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ >> >> This isn't the first time I've shared the link about predictable network >> interface names. >> >> The LFS page discusses a bit of it: >> http://www.linuxfromscratch.org/lfs/view/stable/chapter07/symlinks.html >> >> Disable the assignment of fixed names, so that the unpredictable kernel >> names are used again. For this, simply mask udev's rule file for the default >> policy: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules (since >> v209: this file was called 80-net-name-slot.rules in release v197 through >> v208) >> >> Create your own manual naming scheme, for example by naming your interfaces >> "internet0", "dmz0" or "lan0". For that create your own udev rules file and >> set the NAME property for the devices. Make sure to order it before the >> default policy file, for example by naming it >> /etc/udev/rules.d/70-my-net-names.rules >> >> Alter the default policy file, for picking a different naming scheme, for >> example for naming all interface names after their MAC address by default: >> cp /usr/lib/udev/rules.d/80-net-setup-link.rules >> /etc/udev/rules.d/80-net-setup-link.rules, then edit the file there and >> change the lines as necessary. >> >> Pass the net.ifnames=0 on the kernel command line (since v199) >> >> Does the chapter7 symlink page need an update either referencing the >> freedesktop link or enter a bit in there about how udev will behave? >> >> Or perhaps have it in an introduction page for network setup? > > A little late answering I know, but the kernel boot parameter of > "net.ifnames=0" stops udev creating its own names and produces the > traditional eth0 and wlan0 interface names.
Sorry William, I should have read your post more carefully. I see now that you've already suggested that. Richard -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
