Re: PCI scan problems in 2.2.16

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



At 08:04 AM 7/21/00 +1200, Simon Byrnand wrote:
>At 09:56 AM 20/07/00 -0400, you wrote:
>
>>None of this blabber of yours solves the problem, so why waste everyone's
>>time? Explaining why its broken is kind of like your mechanic telling you
>>why your brakes sqeak. I dont care why they sqeak, i want them to stop
>>sqeaking.
>
>I wasn't explaining why it was broken, I was explaing why relying on a
>specific interface name is broken. As Donald said, they're just arbitary
>labels. They have to be given out in some order - and whatever that order
>is, is never going to suit everyone.

Im sorry, but you're telling me if I plug an intel card in the slot the
onboard ifac is eth1 and if I plug a tulip its eth0, and there is just no
way that that can be correct.


dennis

-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux