Hi Fred,
This looks like a failure caused by insserv being run. Although there
are some third-party packages that are known to misbehave and call
insserv directly, none of these are known to cause this problem to recur
after unrelated system updates.
So the other explanation would be that /etc/init.d/.legacy-bootordering
is missing from your system. Do you have this flag file?
** Changed in: sysvinit (Ubuntu)
Status: New => Incomplete
** Changed in: sysvinit (Ubuntu)
Importance: Undecided => High
** Package changed: sysvinit (Ubuntu) => insserv (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901585
Title:
runlevel links incorrectly numbered sequence
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/insserv/+bug/901585/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
