On 31/03/13 04:06, Philip Webb wrote:
130329 Samuli Suominen wrote:
Attached new version again, more generic than before.
I find this difficult to decipher. Who is it aimed at ?
I've just updated to Udev 200 . Following the news item,
I renamed /etc/udev/rules.d/70-persistent-net.rules :
my script to start my I/net connection with DHCP failed.
I restored the file to its old name & all works as usual :
it has 'NAME="eth0"'.
Aimed to everyone and it already answers your questions. I can answer
them differently here again, but if you read the news item, this all is
there:
If kernel assigns eth0 to first network interface (driver/module) then
you can't rename to eth0, thus the rule you have is likely superflous
and it doesn't matter if you delete it or not -- you are currently
using "random" kernel names
What it might do is interfere with enabling of the new networking, so
you should propably symlink /etc/udev/rules.d/80-net-name-slot.rules to
/dev/null and delete the 70-persistent-net.rules and the behavior of
your system stays exactly as it's when you are writing this now,
using random kernel names, but if it's an system with only 1 network
card, it propably doesn't matter much as eth0 gets always used (almost
always)
Nothing is stopping you from leaving out the symlink either and
migrating to the new name despite using only 1 network card either,
it's still more reliable than the kernel names
The logic really isn't that hard... It's documented everywhere... :-(
