Re: Determining eth -> driver mapping
From: Stephen Patterson (s.patterson_at_freeuk.com)
Date: 09/27/03
- Previous message: Andreas Janssen: "Re: Cannot compile the kernel"
- In reply to: michf_at_post.tau.ac.il: "Determining eth -> driver mapping"
- Next in thread: Micha Feigin: "Re: Determining eth -> driver mapping"
- Reply: Micha Feigin: "Re: Determining eth -> driver mapping"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 27 Sep 2003 09:47:30 GMT To: debian-user@lists.debian.org
On Sat, 27 Sep 2003 00:10:08 +0200, michf@post.tau.ac.il wrote:
> I would rather try to detect which interface is mapped to the driver
> instead of assuming the active one is always on eth0.
> Is there a way to do that?
AFAIK there isn't a way to tell that, but if your network drivers are
all modules, you can prompt the system to always load rtl8139 for eth0
anda different module for eth1. You do this by adding aliases to
/etc/modutils/aliases and running update-module.
This is what I have on my firewall.
alias eth0 8139too
alias eth1 3c509
-- Stephen Patterson http://patter.mine.nu/ steveSPAM@.patter.mine.nu remove SPAM to reply Linux Counter No: 142831 GPG Public key: 252B8B37 Last one down the pub's an MCSE -- To UNSUBSCRIBE, email to debian-user-request@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
- Previous message: Andreas Janssen: "Re: Cannot compile the kernel"
- In reply to: michf_at_post.tau.ac.il: "Determining eth -> driver mapping"
- Next in thread: Micha Feigin: "Re: Determining eth -> driver mapping"
- Reply: Micha Feigin: "Re: Determining eth -> driver mapping"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
