On Mon, 2010-05-10 at 15:29 +0530, Rahul Sundaram wrote: > On 05/10/2010 09:30 AM, Robert C. Lightfoot wrote: > > I raised this point with Alpha and again with Beta, but it's either been > > decided against, ignored or I've failed to state myself clearly. The > > most recent F13.RC2 install when used on a multi-boot Fedora/Windows > > machine setup a grub which had Fedora as default and delay at zero (0). > > This meant to access Windows I had to edit grub from Fedora to change > > the delay to reach windows. > > > > If we are trying to reach and convert Windows users, then when Fedora > > Installer does a multi-boot install the default needs to allow a small > > amount of time to choose the OS and not set the timeout to 0. > > > > This was already the case. If it doesn't happen anymore, then it is a > regression. Have you filed a bug report? Have you marked it as a > blocker? Otherwise, it might be ignored. There's definitely not been a blocker bug for it, but thinking about it, I can confirm the problem - when I installed F13 on this machine it had Windows XP on it, and F13 correctly set up a bootloader config with an entry for loading XP, but set the timeout to 0 :/. I just never really thought about it and realized it was something we really ought to fix for final. At this point we're _probably_ just going to be documenting it, I'm afraid. If not, we certainly have to slip the release a week. If you'd like to argue for the slip to fix this bug, or at least have it formally discussed, please file a bug on this - specifically on the multiboot case, if you open it just against the overall default to 0 it'll probably get closed quite fast :) - and mark it as blocking F13Blocker. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
