On Mon, Jul 27, 2015 at 09:58:58AM -0400, Gene Heskett wrote: > Greetings all; > > I am in the process of building up an old MSI K8M890M2-V motherboard, > with an Athlon 64X2 at 3.8Ghz on it, to be used for cnc machine control, > and while I finally did get networking up and running, I was amazed to > find that udev would create an eth0 on finding an 8139too on the > motherboard, this is in dmesg, but then renames it to eth5! Fixing > my /etc/network/interfaces file to bring up eth5 made it work normally. > > But call me bumfuzzled by that remaning, what genius thought that was a > good idea? > > And I've not found an entry in /etc/udev/rules.d/70-persistent-net that > would explain it. Can someone advise as to the reasoning for that?
I found this: http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ where the first couple of paragraphs has an interesting blurb. Is this on a Jessie system? -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150727153311.GA14419@tal