Jesse Pollard wrote:
>
> --------- Received message begins Here ---------
>
> >
> > Jesse Pollard wrote:
> > > The only way to determine
> > > the ACTUAL eth0 is via mac number and trial and error.
> >
> > not correct, as noted in other e-mail.
> >
> > > I configure ONE interface (all others are down), then plug in to a working
> > > network.
> > >
> > > If I can ping the other machine then I know which network a given
> > > interface is on - label it.
> > >
> > > Now down that interface, and initialize another one. Repeat until all
> > > interfaces are identified.
> >
> > also note that one can rename interfaces, or in the future they might
> > appear out-of-order. To only way to be obsolutely certain where a
> > network device is on the PCI bus is ETHTOOL_GDRVINFO.
> >
> > Jeff
>
> Does ETHTOOL_GDRVINFO work on ISA devices too? Last I knew it didn't. And
> I do run a system with both PCI and ISA network cards.
The interface works fine with ISA, but it might not be implemented in
one particular driver or another. 2.4.18-pre1 supports some but not all
ISA drivers.
Jeff
-- Jeff Garzik | Only so many songs can be sung Building 1024 | with two lips, two lungs, and one tongue. MandrakeSoft | - nomeansno - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Dec 31 2001 - 21:00:25 EST