Package: ifupdown Version: 0.6.7 Severity: important If my computer fails for any reason and I have to reboot without having shutdown properly then upon restart the start up scripts have to run fsck on all the disks.
In this instance, ifupdown fails to bring up all the interfaces, so that once the reboot is complete the computer is isolated from the network. Rebooting again, with a proper shutdown then allows all network interfaces to be brought up properly. It appears to be the interfaces being controlled via hotplug that are the problem. In my case eth0 is the device that fails to come up, although the device eth0 certainly exists after boot (ifconfig eth0 lists the characteristics) I am not really sure why this is the case, and some little exploration has not shown where the problem is. So I am raising this bug against the ifupdown package, but I am not sure that is necessarily the correct place. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages ifupdown depends on: ii debconf [debconf-2.0] 1.5.3 Debian configuration management sy ii libc6 2.3.6-18 GNU C Library: Shared libraries ii net-tools 1.60-17 The NET-3 networking toolkit ifupdown recommends no packages. -- debconf information: ifupdown/convert-interfaces: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
