Message-ID: <4356BCB9.8080904@tmr.com>
Date: Wed, 19 Oct 2005 17:38:01 -0400
From: Bill Davidsen <davidsen@tmr.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.11) Gecko/20050729
MIME-Version: 1.0
To: Arjan van de Ven <arjan@infradead.org>
CC: linux-kernel@vger.kernel.org
Subject: Re: Sequence of network cards
References: <20051019104712.GC9765@kestrel> <1129720556.2822.25.camel@laptopd505.fenrus.org>
In-Reply-To: <1129720556.2822.25.camel@laptopd505.fenrus.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1093
Lines: 26

Arjan van de Ven wrote:
>>Is the algorithm for assignment of eth? numbers by Linux kernel
>>documented anywhere?
> 
> 
> it's generally on a pci bus order. However... if you switch to acpi by
> going from 2.4 to 2.6, the pci bus order might change.
> 
> The good news is that you can do a few things to mitigate this:
> 1) Several distros (including Fedora Core) allow you to bind ethX
> numbers to mac addresses, eg effectively persistent binding of ethX
> numbers to specific cards
> 2) you can rename ethX to ethY yourself with nameif and similar tools.

I knew about nameif, I was unaware of the bind to MAC solution, and 
thank you much for it. As the number of cards goes up it scales easily.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me
-
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/