Something that wasn't entirely clear to me before, but maybe should have
been: the problem may just be in the syntax of the rule that's generated
during the upgrade. (I used do-release-upgrade to go from intrepid to
jaunty.)
Before the boot, here's the rule that's in 70-persistent-net.rules:
# Converted from /etc/iftab on upgrade
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:8d:c0:b9:30",
ATTRS{type}=="1", NAME="eth0"
After boot, that rule is still there but this one has been added:
# PCI device 0x1106:0x3065 (via-rhine)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:50:8d:c0:b9:30", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
If I edit the file, remove the first rule, change the second to use eth0
instead of eth1, and reboot, the device stays as eth0 and everything
works correctly.
So possibly the upgrade just needs to generate the second syntax rather
than the first?
--
upgrading to Jaunty renamed eth0 to eth1
https://bugs.launchpad.net/bugs/329106
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
