Ahhh, you're right. How about looking in dmesg to see what each network interface is? tsmcyf at lildeb:~$ dmesg | grep eth eth0: OEM i82557/i82558 10/100 Ethernet, 00:D0:B7:43:D1:D4, IRQ 11. eth1: Xircom: port 0x300, irq 3, hwaddr 00:10:A4:9A:50:76 tsmcyf at lildeb:~$ On Fri, 07 Sep 2001, Jesse Erdmann wrote: > Are you suggesting I cross-match that with /proc/interrupts? What I see > in my /proc/interrupts lists eth0 and eth1, not the module. Is it the > same for you? Did you have something else in mind to check against? > > Clay Fandre wrote: > > > > Does your ifconfig show you IRQs? (Mine does) If it does, you can cross-match them. > > > > Hi Jesse! > > > > On Fri, 07 Sep 2001, Jesse Erdmann wrote: > > > > > > /proc/modules tells me how many devices are using a specific module, but > > > it doesn't tell me which ones. I really need to know something like > > > ethX is using moduleX. I need to send an ioctl with the name of the > > > device (eth0, eth1, etc). If I use eth1 when eth1 is using some other > > > module, that ioctl might mean something very different to the module > > > eth1 is using. That could cause bad things to happen. > > > > > -- > > Jesse Erdmann > Engineer > Secure Computing Corp. > _______________________________________________ > tclug-list mailing list > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list