Hans composed on 2015-12-29 20:55 (UTC+0100): > and both got the same settings
What makes you sure of this? ... > The only thing, which IMO would explain it, that the EEEPC is newer than the > other one. But then the hardware must talk to the operation system and give > more information to udev or systemd. Does this do such things? Kernel and drivers probe, so, yes, information is given them. An important point is that racing goes on, and hardware varies, so only 100% identical equipment can produce 100% identical results, and only when the procedure is invariant. What drivers and kernels do will vary with versions. Given the same installation DVD, driver and kernel probably is not a factor in your case, but hardware probably is given the different age of the machines. > There was > something mentioned in the doku, but I did not quite understand, what the > doku > meant. I suggest you read it again, and if it doesn't become clear, ask specific question(s) about what remains unclear. > And if enps10 is the "new" kind of naming network devices, is it then > recommended to edit all configurations and change the entries from eth0 to > enp1s0? What is recommended is that if you care about what device names are assigned that you take an active role in the assignment process. Otherwise, let them be whatever kernel and driver choose for them to be, and don't waste time trying to figure out *why* they do what they do. > This would also mean, I guess, either 70-persistent-net-rules must also be > edited or should be deleted. Again, it depends on your interest. It sounds like you care enough that you should take an active role. > But all this makes not clear to me, what makes the decision, when enp1s0 or > when eth0 is going to be created on a system at boot. I don't think it can ever be totally clear to anyone who deals with non-identical hardware. All my installations are created with net.ifnames=0 on installation kernel cmdline, with fixed IP info on installation kernel cmdline, with the result that eth0 is used for the wired ethernet interface. Post-installation I add /etc/udev/rules.d/80-net-setup-link.rules to help ensure it stays as initially configured through subsequent update and upgrade processes. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
