>> >> the way this works is the first driver to be loaded gets eth0. So the >> 3Com you >> compiled into the kernel SHOULD be setup as eth0. > > It does now, but when I had support for both cards compiled into the > kernel, the 3Com card did not get eth0, it got eth1 and the DSL's NIC got > eth0 and I could not think of a way to control this. That is why I now > have only the 3Com card's support built into the kernel, so it gets > configured first. If I add another NIC later, I will probably have to > also compile it as a module and have it get configured in > /etc/init.d/local after the Kingston NIC's config lines. I just don't > know if that is the correct way or the best way to do it. >
yep, that is the way to do it. Although /etc/modules is the usual place to list modules to be loaded at boot time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
