Comment 13 for bug 839595

@ Scott: thanks for the detailed response. It all makes sense now. I am guessing perhaps wicd wrote that entry in my interfaces file. I haven't edited this file by hand.

@ Clint: yes, I think it makes sense to add this to the release notes. Thanks for updating the description. It seems like this is a reasonable approach for now.

Longer term, I think the start system needs more granularity. Ideally, if the network is still not up, most services (except for things like ntp, firewalls, etc) should start anyway. The user should still be able to get X up and running, and be able to login. But the current structure of one upstart hook to all sysvinit services won't allow for that.

Thank you for the great work, and I hope this little extra bit of info benefits other users.

Best!
-- Leo