On Mon, 30 Jan 2006 10:07:26 -0600
John Haller <[EMAIL PROTECTED]> wrote:
> Stephen Hemminger wrote:
>
> > On Sat, 28 Jan 2006 20:31:18 -0800
> > "Ilya A. Volynets-Evenbakh" <[EMAIL PROTECTED]> wrote:
> >
> >
> >>How does one enfrce eth device ordering at run time, when drivers are
> >>compiled
Originally the patch in question was written in following situation:
1. Module support in the Linux/MIPS kernel was broken at that time
2. I had to netboot and go over NFS
The problem was similar to what is described below,
and solution of enforcing order by loading modules in specific order
wasn
Stephen Hemminger wrote:
On Sat, 28 Jan 2006 20:31:18 -0800
"Ilya A. Volynets-Evenbakh" <[EMAIL PROTECTED]> wrote:
How does one enfrce eth device ordering at run time, when drivers are
compiled in?
One thing I have done is to build as modules everything that
I don't want to have the low numb
On Sat, 28 Jan 2006 20:31:18 -0800
"Ilya A. Volynets-Evenbakh" <[EMAIL PROTECTED]> wrote:
> How does one enfrce eth device ordering at run time, when drivers are
> compiled in?
>
Don't depend on the name! Use tools that use the MAC address.
Several distro's do that, and you can but logical names
How does one enfrce eth device ordering at run time, when drivers are
compiled in?
Jeff Garzik wrote:
> Martin Michlmayr wrote:
>
>> From: Ilya A. Volynets-Evenbakh <[EMAIL PROTECTED]>
>>
>> Move meth.o upwards in Makefile since it's built-in and should be eth0
>>
>> Since meth is the built-in Et
Martin Michlmayr wrote:
From: Ilya A. Volynets-Evenbakh <[EMAIL PROTECTED]>
Move meth.o upwards in Makefile since it's built-in and should be eth0
Since meth is the built-in Ethernet card on SGI O2 it makes sense for
it to be eth0, even if there is also another network card in PCI slot.
Therefo
