Hi Ben, first, sorry that you're having an infuriating user experience.
I wrote that message and it was most certainly not my intention to
infuriate anyone.
The file where that message lives is /etc/init/failsafe.conf, which
belongs to the upstart package, so I'm reassigning the bug as such.
There is definite room for improvement, and I think you've suggested a
few excellent pieces of information that could be added. We could,
indeed, take a look at the interfaces that are not yet up and add those
to the status message. Please understand, before this message existed,
the boot would have raced with all of that network configuration, so
interfaces would have been appearing at any point during the boot, which
led to even more infuriating non-deterministic behavior.
I will ask that you separate your emotions from the facts in future
communication on the issue. There is a lot of frustration in the bug
description, and I understand that. However, we aren't going to be
productive if we can't communicate effectively.
** Package changed: ifupdown (Ubuntu) => upstart (Ubuntu)
** Changed in: upstart (Ubuntu)
Importance: Undecided => Medium
** Changed in: upstart (Ubuntu)
Status: New => Triaged
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
