Bug#403706: marked as done ((sometimes?) fails to bring up interfaces on bootup by default)
Your message dated Wed, 4 Apr 2007 05:44:21 -0700
with message-id <20070404124421.GF17393@dario.dodds.net>
and subject line (sometimes?) fails to bring up interfaces on bootup by default
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: (sometimes?) fails to bring up interfaces on bootup by default
- From: Bastian Venthur <venthur@debian.org>
- Date: Tue, 19 Dec 2006 08:51:28 +0100
- Message-id: <20061219075128.26671.95928.reportbug@hades.beechen.net>
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 libc6 2.3.6.ds1-8 GNU C Library: Shared libraries
ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip
ii net-tools 1.60-17 The NET-3 networking toolkit
ifupdown recommends no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
- To: 403706-done@bugs.debian.org
- Subject: Re: (sometimes?) fails to bring up interfaces on bootup by default
- From: Steve Langasek <vorlon@debian.org>
- Date: Wed, 4 Apr 2007 05:44:21 -0700
- Message-id: <20070404124421.GF17393@dario.dodds.net>
Documentation for the problem of asynchronous network initialization has
been committed to the release notes CVS.
As noted in the bug log, the problem that was preventing network interfaces
from being initialized *altogether* on boot has been resolved separately in
udev.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon@debian.org http://www.debian.org/
--- End Message ---
Reply to: