I agree with your position Steve. "starting rc-sysinit" is actually a more accurate representation of the intent of failsafe anyway. Once rc- sysinit has been started, we're no longer in danger of waiting forever. There is the danger that some other job that is 'start on starting rc- sysinit' then stops rc-sysinit, but that would be a bug in that job if it didn't also do something to move booting forward, so I think this is a safe path to take.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950662 Title: Waiting for network message on bootup when all network devices are up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/950662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
