Re: stock kernel 2.6.12 eth0/eth1 swapped
On Sat, 2005-12-10 at 15:05 -0500, Rich Johnson wrote:
> On Dec 10, 2005, at 9:23 AM, Wolfgang Pfeiffer wrote:
>
> > On Fri, Dec 09, 2005 at 10:06:37PM -0500, Rich Johnson wrote:
> >> I've hit another snag trying to get etch up and running on my G4
> >> Cube.
> >> [...snip...]
> >> The bottom line is that a 2.6.12 stock kernel cannot access the
> >> network.
> >
> > I have definitely a problem with believing that one ... :)
>
> Yeah, so did I, but Im still frustrated. So, let me be more precise:
> - The bottom line is that the 2.6 kernel's introduction of unstable
> network device names breaks pre-existing network configurations
> without warning and there is no ready guidance on how to fix the
> problem.
Network device ordering has never been guaranteed nor stable. It depends
on things like link order, module load ordering, or on async probe
busses like firewire or USB can depend on the phase of the moon.
The bug is to assume it can be relied upon in the first place. I know
it's annoying but that's how it is.
Ben.
Reply to: