Agree: A more stripped-down grub2-package is appropriate for servers. Also, for either servers or desktops: There should be a setting in /etc/default/grub, called GRUB_RECORDFAIL_TIMEOUT or GRUB_TIMEOUT_AFTER_BOOTFAIL or something. This is today effectively hard coded to -1 (forever). And it is this hardcoding many users fiddle with. Conclusion: go from hardcoded setting to configurable option.
I propose that the bootfail-timeout is set to 30 sec by default for servers, perhaps also for clients. This is not unlike how it is on a different OS we all know: after a failed boot, you're halted for 30sec at the boot menu, but then the default entry boots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872244 Title: grub2 recordfail logic prevents headless system from rebooting after power outage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/872244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
