[lkml]   [2001]   [Nov]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: A return to PCI ordering problems...
On Tue, Nov 20, 2001 at 09:27:37PM +0000, David Woodhouse wrote:
> Why must the motherboard be set to eth0? Why not just configure it as it
> gets detected?

There are a couple reasons. One that is specific to this
particular case is that the VeryExpensiveProprietaryPackage
someone bought checks the eth0 MAC address to be sure you
haven't moved it. It would not really be smart to license
it against a removable, swappable PCI card.

In general: I have more than once gotten bitten late
in the night modifying kernels where I switched something
from modular to non-modular and lost communication with
the machine when it came back up. At 4am these things *do*

I'd really not mind the ability to say MAC addresss X is
by definition ethY. That would work for me because the only
way you get screwed is if you change the NIC. And if you
are swapping out hardware, you are usually physically present
to sort things out if your network gets effed.

> If you really care about the names, there's an ioctl you can use to change
> them. You can call them 'fred' and 'sheila' if you so desire.

The iproute2 commands another fellow mentioned look
like they will do the job nicely for my particular
immediate problem.

In the more general case though, I can see a need to
explicitely force or override assignments in special

Nuke bin Laden: Dale Amon, CEO/MD
improve the global Islandone Society
gene pool.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:13    [W:0.079 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site