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 > scripts when configured to do so. Of course kernel does it, but what I mean is something different. Not low-level kernel events. I meant that init script asks kernel to do that thing, and after that udev calls its hooks. > > 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. > Which situation? What should udev do? When net.agent is called before /run/network is ready. What should it do? Don't know yet, that's why I wanted to hear your opinion on this. > BTW, I think that /lib/udev/rules.d/80-networking.rules and the > related scripts should be moved to the ifupdown package. Not a good idea. There can be other things causing interfaces to go up, but that doesn't mean such things should go to ifupdown. > > Oh, forgot the rest of the story. The interface gets up before > > resolvconf is ready, so this doesn't result in dns-* options > > applied. > net.agent is supposed to wait for lo to come up before calling ifup > for the hotplug-enabled interfaces (which sucks, but it is the best > we can do without upstart/systemd), which is supposed to come up when > S13networking runs ifup -a. > What has been broken? It apparently doesn't work. I can't see why do we need to do that at all now, as networking init script brings hotplug interfaces up itself if they are ready at that time. -- WBR, Andrew
signature.asc
Description: PGP signature
