The new version seems to work.
Many thanx to all
Harri
signature.asc
Description: OpenPGP digital signature
severity 676183 critical
affects 676183 resolvconf
thanks
Marking this bug as critical. It breaks DNS configuration, causing
everything that needs DNS to fail when the system is rebooted after an
upgrade.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Hello,
On Fri, 22 Jun 2012 04:51:56 +0200
m...@linux.it (Marco d'Itri) wrote:
The problem is that udev emits events for network interfaces as a
part of a boot sequence, and its scripts call ifup for those
interfaces. lo
No: the kernel emits events for network interfaces, udev merely runs
reassign 676183 bridge-utils 1.5-3
retitle 676183 bridge-network-interfaces should not do anything before ifupdown
is configured
Hello,
On Fri, 22 Jun 2012 11:23:58 +0200
Andrew Shadura bugzi...@tut.by wrote:
It apparently doesn't work. I can't see why do we need to do that at
all now, as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
reassign 676183 udev 172-1
thanks
Hello,
On Wed, 20 Jun 2012 20:34:57 +0200
Harald Dunkel ha...@afaics.de wrote:
Both timing and boot history might be important here. Instead
of manually starting the resolvconf and networking init scripts
I
Hello,
On Thu, 21 Jun 2012 16:12:33 +0200
Andrew Shadura bugzi...@tut.by wrote:
Both timing and boot history might be important here. Instead
of manually starting the resolvconf and networking init scripts
I would suggest to boot a _real_ system.
Yes, boot history is important indeed.
On Jun 21, Andrew Shadura bugzi...@tut.by wrote:
The problem is that udev emits events for network interfaces as a part
of a boot sequence, and its scripts call ifup for those interfaces. lo
No: the kernel emits events for network interfaces, udev merely runs
scripts when configured to do so.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Both timing and boot history might be important here. Instead
of manually starting the resolvconf and networking init scripts
I would suggest to boot a _real_ system.
For verification I have configured a private network with some
fake IP addresses on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maybe its related to configuring a bridge interface. Andrew,
have you tried a bridge, or was your test on eth0?
Regards
Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
On Tue, 19 Jun 2012 20:33:49 +0200
Harald Dunkel ha...@afaics.de wrote:
Maybe its related to configuring a bridge interface. Andrew,
have you tried a bridge, or was your test on eth0?
I've just tried to reproduce it within some test
I've got the same problem with resolvconf, after booting the
nameserver configured /etc/network/interfaces doesn't end up in
/etc/resolv.conf. In my case the dns information is also configured on
a bridge and a manual ifdown br0;ifup br0 gives me a correct
/etc/resolv.conf.
--
To UNSUBSCRIBE,
Hello,
On Wed, 6 Jun 2012 09:38:18 +0200
Thomas Hood jdth...@gmail.com wrote:
I didn't know about the recent ifupdown changes -- thanks for the
tip.
Reassigning to ifupdown.
Ifupdown maintainers: Please let the resolvconf maintainers know if
resolvconf needs to change as a result of
12 matches
Mail list logo
