On Fri, Jan 13, 2012 at 08:42:12AM -0000, Adam Stokes wrote:
> If we think about moving insserv out of system path we need to make sure
> that update-rc.d is not broken by this since it assumes it can reach the
> binary within the path. Other than that I dont think anything else
> would be affected.
In fact, update-rc.d only ever calls insserv if
/etc/init.d/.legacy-bootordering does not exist, which it should for all
Ubuntu systems:
if ( ! -f "/etc/init.d/.legacy-bootordering" ) {
info("using dependency based boot sequencing");
exit insserv_updatercd(@ARGV);
}
Having update-rc.d fail for users who have manually removed this file is
probably the lesser evil, and fixable by having them re-create the flag
file.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[email protected] [email protected]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858122
Title:
incomplete migration to /run (shutdown script order has been
demolished)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
