-----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 would suggest to boot a _real_ system. Yes, boot history is important indeed. I've traced it down. 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 is explicitly blacklisted there, eth0 isn't present in your configuration file, and br0 is ifup'ed before resolvconf had a chance to set things up. I guess, udev should somehow detect this situation and block these events. Let's see what Marco thinks of this. - -- WBR, Andrew -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCAAGBQJP4yvRAAoJEG6k0jEaLSaN29UP/2QupDyTUGhl/NbzsK1j/6vz rSiPMXkct7f4CWjhjUNUBJGfQIYts20Jdmwx53KwrBm1uf4+ZE7c1D66C21lMJAO ZG/Eyejcht7e/YsQQ397fyY/NsI8b5wld1zfVqHLrSG7xw1yyq3k9vx26NZRDIo/ 9ldGqJCvqloXCIb4JB69BdfYMwaoZmIPj8Pli34Z4d8UUHJyocfn4li3KXavOI27 QdU/7YawdZ3/wlGm4yyv+u5T6Xgn71klEfkLUaQKYvId/aDBEoCUNJDlyYqYtZUT 9FZD2f2Ty+/bCuDabXV+YFhgp8CWZ5RgYkhLeeegubZkabckGSEDq7TFVYGjWFtS xUVBQ2GRswx5qnIJNDCv0WzUcw6oemM2KiOrRbp2zo6titXW4v5yA5S2aX06FWzT UiXflRegHyUnAqA67RHSB9SCqscCHgxZYcLSwOnjYETh+0ozwVHv/THe/dzS5CDf SDmZ9MOeFfgaE4AkfAKnwRIYQVPgqLoeEAF0KcIZOM23MN9+h2ik5sRklu3BcBSe h1yARHGko+FesFZqMp2d4qDaDym+/CAAhXHCSFEa0Rv5x/BMkAk1nHxViSCl/FI1 6N5gERUwOm/S2LZQzVIQv+npwhfLsOl0oWunvphEJbJQ3YpBKg4nDkJBqEIS9RK+ y/w8pOw1hxEifmnkXr1f =m4Nk -----END PGP SIGNATURE-----
