On 07/31/2015 06: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.
I usually write our iso image to a USB stick with dd, then just boot all the candidate machines from that USB stick. I use the Live mode (which mounts the USB stick read-only) to test latency on new hardware, this works great. > 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. Udev tracks network interfaces it has seen in /etc/udev/rules.d/70-persistent-net.rules. If you rm that file, it'll forget all about the NICs it has seen. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
