Brian,
I'm not sure exactly. What I observe is that for some reason, only one
interface gets written to iftab during the default install out of the box.
My hunch is that when the install script is populating iftab, it doesn't
know about the other interfaces, perhaps because the other interfaces aren't
up at that stage of the installation or because the drivers sufficient to
talk to the other interfaces aren't yet installed. Later, when the other
interfaces are up and running, udev recognizes the additional device(s), but
there is no matching iftab record, so udev goes about its business as usual.
The manpage for iftab says:
If a network device matches all selectors of a mapping, udev will
rename the interface to the name given by the mapping.
I think the following additional logic would Do the Right Thing (tm):
If the device does not match all the selectors of any mapping, [some script]
will write a record to iftab that names the device intelligently and
contains the selectors matching the device. A message is written to syslog
describing the device and the new iftab record (e.g., "New network interface
detected and named [eth1, or whatever]. Persistent name record written to
/etc/iftab.").
Loye
On 6/7/07, Brian Murray <[EMAIL PROTECTED]> wrote:
>
> Loye Young - do you happen to know how this came about happening though?
>
> --
> ifconfig fail to load 3coms 3c905C-TX/TX-M [Tornado] lan card
> https://bugs.launchpad.net/bugs/118368
> You received this bug notification because you are a direct subscriber
> of the bug.
>
<[EMAIL PROTECTED]>
--
ifconfig fail to load 3coms 3c905C-TX/TX-M [Tornado] lan card
https://bugs.launchpad.net/bugs/118368
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
