In some cases, /etc/init.d/NetworkManager can block boot in a way that is not good. 

Let's say you have a WiFi connection configured to "Public WiFi". And let's say it connects fine at the coffee shop, but not at home. If this is your last selected WiFi AP, then when you start up at home, it is possible that the initscripts will freeze as everything waits for NetworkManager to try to connect to "Public WiFi" (which never happens.)

Ideally, NetworkManager would not block even network-dependent scripts from starting. This is a regression. I originally turned off this 'hard network requirement', as many scripts that USE a network don't NEED a network to be active.

NetworkManager startup should be adjusted to start a network but not block network-dependent services.