Building a PC Isn't Hard

[Michael Hipp]

Lonni J Friedman wrote:
> On Feb 4, 2008 5:58 AM, Michael Hipp <Michael at hipp.com> wrote:
>> vu pham wrote:
>>> kwall at kurtwerks.com wrote:
>>> [...]
>>>> I've got a similar GigE NIC:
>>>>
>>>> Driver: r8169 Gigabit Ethernet driver 2.2LK loaded
>>>> NIC: RTL8168b/8111b
>>>>
>>>> Perversely, it loads at eth0, but gets configured at eth2. No, there
>>>> are no other NICs in the machine. Not sure if it's a driver problem
>>>> or a configuration problem in the OS.
>>> Here is what I have in my notebook's dmesg:
>>>
>>> eth0: Tigon3 [partno(BCM95755m) rev a002 PHY(5755)] (PCI Express)
>>> 10/100/1000Base-T Ethernet 00:1c:23:95:99:6c
>>> eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
>>> eth0: dma_rwctrl[76180000] dma_mask[64-bit]
>>> net eth2: device_rename: sysfs_create_symlink failed (-17)
>>> udev: renamed network interface eth0 to eth2
>>>
>>>
>>> and it ends up using eth2 after boot. Don't know why the kernel changed
>>> it from eth0 to eth2. The system does have a Dell 1505 Draft 802.11n but
>>> it is never detected.
>> You guys need to use a proper distro with an /etc/iftab file.
>>
>> Linux is about having choices, like being able to choose which eth my
>> nic lands on.
> 
> That's what /etc/sysconfig/network-scripts is for.  I'm assuming that
> iftab is some debian abomination.

I wouldn't know, I run Ubuntu! Hehehehe.

But it sounds like our friends above are so disadvantaged they are 
forced to run some third-string wannabe that can't even keep it's ducks, 
er eths, in a row. Maybe we should take up a collection to buy them a 
CD-R with a decent distro on it.

Michael