The reason we can't re-use reserved interface names is because at the
point at which we're activating an interface, we don't know whether the
interface that reserved the name is going to be activated later or not.
It's not just removable devices, ordinary PCI devices can be activated
in either order at boot time depending on sunspot activity.
For feisty, I'm going to investigate the new "static interface names"
scripts in Debian and SuSE as replacements for /etc/iftab -- these
assign a name to the card when it's first inserted, and forever reserve
that name -- however this still wouldn't fix this bug for you.
The "new card" would get the name eth1 or eth2, and your configuration
would have to be adjusted accordingly.
There's no useful warning here either, because for most laptop users,
this swap of eth0 and eth1 is a normal part of their boot process.
** Changed in: udev (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Scott James Remnant
Status: Unconfirmed => Confirmed
--
Dapper doesn't report iftab MAC address error
https://launchpad.net/bugs/53936
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
