I've had a lot of grief over the last week caused by just this same problem.
I have a headless server with a Mini-ITX m/board which has been running very happily for a year or so. Up until a week ago, it hadn't been re-booted for 3-4 months. I then had occasion to re-boot it (because I'd replaced a failing fan) and after the re-boot - no ethernet connectivity. I spent a long time thinking it was a hardware problem until eventually I booted the box with an up-to-date Sarge installation CD. As part of the startup process it asked, "Which of your ethernet cards do you want to use?", which surprised me as I only had one. It did however give me the clue as to what was wrong. Somewhere in the process of tracking Sarge updates (and some time in the last 3-4 months) the priorities have changed. Where before the system used the ethernet hardware for eth0 it now chooses to use the Firewire port instead. This is without any configuration changes on the box - just software updates. This bug most definitely should not have a "wontfix" attribute. Imagine a headless server in a dark data-centre. All it needs is routine updates and a re-boot and the thing is totally FUBARed. This is *not* the sort of behaviour one expects of a Debian installation. What's described here is a serious bug and it needs attention. I would be delighted to look at it if you could provide me with some guidance about how hotplug decides what order to assign to network devices. John Winters -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
