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.
> 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? BTW, I think that /lib/udev/rules.d/80-networking.rules and the related scripts should be moved to the ifupdown package. > 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? -- ciao, Marco
signature.asc
Description: Digital signature
