This "feature" makes no sense to me. I've been using Linux on servers since Slackware came on a stack of floppies. Any sysadmin worth their salary will tell you it's an extremely bad decision to let the server hang if it was improperly shut down. I want my servers to come back online after an issue, why are you keeping them offline?
One of my 12.04 servers is crashing regularly due to a 3.2 kernel bug. EVERY SINGLE TIME someone needs to walk all the way there and hit the reset button. Lost power once - same thing, Ubuntu won't come up; but Windows did; Red Hat did. This is revolting. Please, please, please, remove this caricature of a "feature" from a distribution meant for servers. Please ask experienced sysadmins before making such changes. A server should come up ALL BY ITSELF whenever possible. Do not prevent it from doing so. I will update the kernel to a non-buggy version and reconfigure grub to not hang anymore, but meanwhile this distribution is installed on numerous of servers around the world and causes unnecessary downtime because of a nonsensical decision in a package somewhere. :( Ubuntu team, you have really let the ball drop on this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/797544 Title: grub2 waits forever for keystroke before booting default OS. headless server. hang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/797544/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
