On Wednesday 15 January 2003 04:31, Ron Stodden wrote: > H.J.Bathoorn wrote: > > On Tuesday 14 January 2003 13:12, Ron Stodden wrote: > >>It is kernel that assigns eth numbers at boot time, I suspect based on > >>the (remembered) MAC at the other end of the link, using arp (see man > >>arp), and the eth number assigned by kernel has nothing to do with the > >>NIC type, NIC manufacturer, or PCI slot. I suspect that the NIC is > >>never aware of its eth number - communication is done MAC to MAC, which > >>is why the MAC is assigned by the NIC manufacturer on a globally unique > >>basis, although it can be programatically changed (and the low order > >>byte is dynamically changed as part of the cable modem protocol). > > > > You are quite right, I didn't write that down as specifically as I > > should've. > > > > It isn't as much as in which order the kernel sees the nics during the > > install procedure but how the "available drivers list" is ordered. > > I cannot agree, since the NIC driver module is inserted based on the > line in > /etc.modules.conf, such as: > > alias eth1 tulip > > This indicates that the eth number has already been assigned when the > driver > module is inserted.
Were still talking about the initial install aren't we? Afaik /etc/modules.conf's content hasn't been written yet i.e. is about to be written. Good luck, HarM
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
