Robbie, it's a regression. In previous release, you would screw up your interfaces file, the system would still boot, only there would be no networking. Mistake do happen, failing gracefully is the right thing to do when possible.
What I do not understand is: why is a problem with networking preventing getty to be spawned on the console? It is completely counter-intuitive, it just does not make any sense. I understand it's how Upstart behave, but if services are failing on completely unrelated service not starting, that's pretty brittle. Can we make it more robust please? -- Mistake in /etc/network/interfaces keeps the system from booting https://bugs.launchpad.net/bugs/512253 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
