[Pkg-sysvinit-devel] Bug#710747: sysvinit startup dependencies when using network-manager

[Petter Reinholdtsen]

[Roger Leigh]
> Shouldn't the network-manager init script be blocking until that's
> happened?  Isn't that one of the guarantees which $network should be
> providing?  At least, if it was claiming to provide $network which it
> currently doesn't.

There is no way to guarantee that.  The only guarantee that can be given
is that the local interface is up.  If you want to run a script when the
network is up, it need to go into if-up.d/, not init.d/.

Welcome to the new dynamic world of event driven Linux.

Static dependencies and sysv-rc can only take us so far, and handling
events when the network come up is unfortunately out of reach. :)

> So it's not clear to me how any service depending on $network would
> guarantee any networking when using network manager--it could be
> ordered after any of these services.

Actually, even ifupdown can not give such guarante when dhcp is used.

Programs need to cope with network coming and going, both during boot
and after boot.

-- 
Happy hacking
Petter Reinholdtsen