On Wed, May 23, 2007 at 20:09:49 -0500, Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote: > >>>>> "JK" == Jesse Keating <jkeating@xxxxxxxxxx> writes: > > JK> I talked with Jeremy about this today and he said that lots of > JK> painful history has shown that 10 seconds is the optimal time out. > > Which would be another ten seconds uselessly wasted. Why can't we set > the timeout be as short as possible while still allowing it to be > interrupted in the case of something truly terribly bad, and let the > code that runs after grub is done accept input and perhaps reboot to > grub with a longer timeout if necessary. It certainly has plenty of > time while the rest of the boot process runs. Because if the OS is borked, you might not be able to interrupt that next process. Also if you are sitting at the console, can just hit the enter key. There probably should be a simple way to change it post install for people that want the shorter boot times but don't know to edit grub.conf. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
