Hi Clint, thank you for the quite civil response to what was an emotionally charged description. I should have waited to read over the text in a less stressful environment. I apologize; the description was out of line.
Thanks for pointing out the source of message. In addition to the suggestions I made in the bug description, it seems reasonable that any error message should identify its source. I don't mind having to sift through code to debug an issue but as things are it's not even clear where to begin looking. It seems this issue and many like it are as much documentation issues as they are user interface issues. The integration (and, in this case, behavioral improvements) that comes with a modern init system is great but often makes debugging issues quite difficult due to the large number of components involved and the lack of a comprehensive description of how the pieces interact. When error messages pops up from a piece of code which doesn't identify itself, one has litttle recourse but to grep the entire filesystem and hope that the message turns up. The Upstart Cookbook is a great resource, but it doesn't explain how Upstart is used in Ubuntu in particular. I'm not sure where such documentation would belong, but it seems that the world would be a better place if there were a document describing the various Upstart tasks critical to Ubuntu's boot process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261765 Title: "Waiting for network configuration" is a woefully inadequate message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1261765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
