I had symlinked net.lo per wiki and usual instructions. I removed symlink /etc/init.d/net.eth0 > net.lo and copied net.lo to net.eth0 and system came up with the nic._________________Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting.

, but now I can't SSH to the Pi any more. Restarting the SSH service fails, so it is fair to say that I have not managed to fix this with my workaround.

Questions:
1. Why on one Pi and not on the other? It is a difference in hardware builds?
2. Is there a fix that will guarantee that the NIC is operational after boot-up, no matter what?_________________Ultra5-360 1GB Ram, Ultra5-333 380MB, Ultra10-440 192MB - all Gentoo Linux. And now loads of Raspberry PIs!
Remember Kids, it's always fun until someone gets hurt. Then it's utterly hilarious!

The content of the file /etc/udev/rules.d/70-persistent-net.rules varies on the MAC address of the eth0-device. So lifting-and-shifting an SDCard with this file from one PI (model B) to another causes it to be "non-compatible" on the new device. The UDEV service adds another line to this file for eth1-device, eth2-device and so on every time the SDCard is inserted to new PI.

Is there a way to fix UDEV's behaviour to rather replace the existing line, so that I always have just eth0 when I insert the SDCard into a new PI? Or is the only solution to summarily remove the /etc/udev/rules.d/70-persistent-net.rules file every time the PI boots?_________________Ultra5-360 1GB Ram, Ultra5-333 380MB, Ultra10-440 192MB - all Gentoo Linux. And now loads of Raspberry PIs!
Remember Kids, it's always fun until someone gets hurt. Then it's utterly hilarious!