rc1 + kudzu-0.70-1 I installed rc1 on a system with 3c509, so that I had alias eth0 3c509 in modules.conf This nic, being ISA, was not in hwconf, so kudzu did not know it. Took the HD out and put into a system with a 10/100 pci card (DLink/Macronix) that need tulip module. Kudzu said I had a new hardware (the new nic) and if I wanted to configure it. In an ideal world kudzu would have asked me If I had replaced the card, so that it would have already known the ip address stuff; I understand this is due to 3c509 being ISA, maybe it could look at /etc/modules.conf? Configured it (gave same ip address of the 3c509). Kudzu: - added "alias eth1 tulip" to modules.conf - setup ifcfg-eth1 - updated hwconf Now (no network modules loaded): - network start -> eth0 failed, eth1 failed, loaded tulip - network stop - network start (tulip already loaded) -> eth0 OK, eth1 failed The 1st "network start" loads the tulip module, and fails, the 2nd one uses the tulip loaded by the 1st. A normal boot does not bring the network up properly. So now, even if I have "alias eth1 tulip" in modules.conf, I have networking up with the tulip card being recognized as eth0 (ifconfig eth0 shows the pci card). Then I took the HD out, and re-installed on the original system. kudzu says "do you want to remove the settings for macronix"? I say yes. It removes it from hwconf, but alias eth1 tulip ifcfg-eth1 (onboot=yes) are still there, so that I have a "failed" on boot for eth1 (the 3c509 comes up ok, though).
Ok, this is a very weird case, and difficult to re-test in new releases (even for me) so I'm closing this.