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

Roger Leigh rleigh at codelibre.net
Tue Jul 16 19:29:44 UTC 2013


On Tue, Jul 16, 2013 at 11:33:37AM +0200, Daniel Baumann wrote:
> I don't see what could be done in tftp-hpa to address the issue, it
> declares the network depends in the lsb header of the sysvinit script;
> if sysvint then doesn't do the right thing (anymore) when NM is
> installed, then this is either a bug in NM or in sysvinit, reassigning
> to sysvinit.

Does

  echo '$network network-manager' > /etc/insserv.conf.d/network-manager
  insserv

fix things; or alternatively

  edit /etc/insserv.conf to read
    $network        +networking +ifupdown +network-manager
  run insserv

The former will allow network-manager to provide the "$network" virtual
service directly.  The latter hard codes it into the main insserv
config which is less flexible--it's mainly restricted to the scripts
provided by initscripts itself.  If the former works, that's preferable
I think.

This is the most obvious defect I can see.  It's kind of a major one
though--I'm very surprised that such a fundamental defect wouldn't
have been picked up sooner.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux    http://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-    GPG Public Key      F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800



More information about the Pkg-sysvinit-devel mailing list