On 7/10/07, Scott James Remnant <[EMAIL PROTECTED]> wrote:
>
> Network cards are assigned persistent names the first time they are
> inserted, and they keep that name forever after unless you manually
> modify /etc/udev/rules.d/70-persistent-net.rules (gutsy onwards) or
> /etc/iftab (feisty and bef
Scott James Remnant:
> the suggested log message would be output every time on boot anyway
I'm not quite sure which suggestion you refer to, but the way I see it,
providing some information in the case where there is a mismatch between
the interfaces listed in /etc/iftab and interfaces present on
Network cards are assigned persistent names the first time they are
inserted, and they keep that name forever after unless you manually
modify /etc/udev/rules.d/70-persistent-net.rules (gutsy onwards) or
/etc/iftab (feisty and before).
This is correct behaviour; since most modern laptops have two
Just to say 'me too'. (I've marked my bug 69773 a duplicate of this one;
I've also listed other possible duplicates in the comments for 69773).
This was difficult to track down, and it'd be good if there was a
warning if any interface is hidden because of an iftab entry, and/or
udev would warn abo
Good point about PCI devices being activated in semi-arbitrary order.
That's what makes it necessary to have this database in the first place,
I suppose.
I would be happy enough if dmesg and/or syslog reported hints when a new
MAC address was added to the db, and to report which MAC was assigned t
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 ord
** Changed in: Ubuntu
Sourcepackagename: None => udev
--
Dapper doesn't report iftab MAC address error
https://launchpad.net/bugs/53936
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ditto for Kubuntu 6.06 when I changed motherboards.
Mathworks Matlab activation script uses the MAC address for eth0 to
activate its software. Kubuntu had gone ahead and assigned the new card
to eth1 so Matlab activation script failed (this is a bug in their
activation script as much as it is a Ub
We had the same problem with /etc/iftab file when we used one computer
to create an image of the hard drive and then copied that to new
computer. So I second that this is a real problem and something should
be done for it.
--
Dapper doesn't report iftab MAC address error
https://launchpad.net/bug
I and my colleagues deal with ubuntu images/restores and the current
udev/iftab behaviour has caused us a fair bit of grief for the same
reason.
Currently, a backup or image isn't usable by another machine without
manually editing iftab. That isn't obvious to users, I think.
One solution is to w
10 matches
Mail list logo
