Gene, I got bit on a Gentoo upgrade some time back. There is a way to force udev to use specific addresses instead of things like net.e13sp5, but Iforget how to do that. Since I only have to deal with this when I change the net hardware, I decided not to fight it and just deal with it. As a note, when I stumbled onto this there was some long discussion and justification on why this was a good thing. I did not delve into the nasty bits and just accepted it. If you look around a little you can find out how to go back to the old behaviour.
EBo -- On Jul 31 2015 6:24 AM, Gene Heskett wrote: > A heads up of sorts. And really has nothing to do with LinuxCNC > itself, > just the installer. > > In the process of finding a machine suitable to use as a linuxcnc > host, I > ran into a thing with udev that was quite a pain in the ass until I > discovered the reason. > > Moving the drive, with the latest updated install on it from machine > to > machine, I had networking failures anew everytime I moved the drive. > > It seems some genius in charge of udev thought the interfaces should > be > renamed everytime the hardware changes, so udev, in its infinite > wisdom, > dutyfully finds and loads the correct driver for the hardware it has > found. But some unknown place, it keeps track of how many different > hardwares it has found, so since it had, by the time I wound up with > it > in the current machine, found several different families of hardware, > it, quite a few lines on down in the dmesg report and easily missed, > renames it, in the most recent machine, to eth5! Since my local > network > is hosts file based, I had to edit (after nuking network-mangler with > extreme prejudice) my /etc/network/interfaces file so it used eth5. > > I have no idea what udev genius thought that was a good idea, but if > it > can be found and fixed to not do that in the next respin, it would > sure > be a lot better than a whole bottle of excedrin. > > I'll also tip my hat to whomever fixed the installer so it would > accept a > handmade partition, its the first time in several installs that I was > able to actually setup and use a /boot partition as the first > partition > on the drive. The bios on the first of the machines I tried wouldn't > boot, couldn't reach far enough into the drive to find the boot > files, > and a separate sda1=/boot partition just works. > > Cheers, Gene Heskett ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
