Bug#403706: (sometimes?) fails to bring up interfaces on bootup by default
On Tue, Dec 19, 2006 at 08:51:28AM +0100, Bastian Venthur wrote: > Hi ifupdown-Maintainer, > I've installed a recent Debian/Testing on two different boxes and on a > virtual qemu-box and the following problem appeard on all of them: After > booting the system the nentwork inteface is not brought up correctly > which makes this installation (in fact the whole system) unusable for > reomote-only installations. > The problem seems to be the following line in /etc/network/interfaces: > allow-hotplug eth0 > Issuing an > sudo ifup -a > does not do anything. > After changing the line to > auto eth0 > the problem seems to be fixed. Please note that I'm not talking about > some heavyly customized installations but rather about default > installations of an up-to-date Debian/Testing. > I've mentioned the problem on d-devel and d-user-german and it looks > that the problem (as well as the proposed solution) is quite common. But isn't this a regression in the installer for using an allow-hotplug stanza, not in ifupdown? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403706: (sometimes?) fails to bring up interfaces on bootup by default
Package: ifupdown Version: 0.6.8 Severity: critical Tags: patch Hi ifupdown-Maintainer, I've installed a recent Debian/Testing on two different boxes and on a virtual qemu-box and the following problem appeard on all of them: After booting the system the nentwork inteface is not brought up correctly which makes this installation (in fact the whole system) unusable for reomote-only installations. The problem seems to be the following line in /etc/network/interfaces: allow-hotplug eth0 Issuing an sudo ifup -a does not do anything. After changing the line to auto eth0 the problem seems to be fixed. Please note that I'm not talking about some heavyly customized installations but rather about default installations of an up-to-date Debian/Testing. I've mentioned the problem on d-devel and d-user-german and it looks that the problem (as well as the proposed solution) is quite common. Cheers, Bastian -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages ifupdown depends on: ii debconf [debconf-2.0]1.5.8 Debian configuration management sy ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip ii net-tools1.60-17 The NET-3 networking toolkit ifupdown recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
