Linked by Thom Holwerda on Tue 18th May 2010 21:35 UTC
Fedora Core "No, Fedora 13 Linux is not coming out today. The release was pushed back by a week to fix a number of blocker bugs, among them is an interesting one that many users might simply consider to be just a papercut nuisance."
Order by: Score:
Not a blocker...
by Delgarde on Tue 18th May 2010 22:59 UTC
Member since:

According to one of the comments on the article, this one wasn't actually one of the blockers - just something judged important enough to be worth fixing given that the release was already being delayed.

Reply Score: 4

Comment by dayalsoap
by dayalsoap on Wed 19th May 2010 04:17 UTC
Member since:

I'm newer to Linux. How would one boot to Windows without the boot menu?

Reply Score: 2

RE: Comment by dayalsoap
by evert on Wed 19th May 2010 07:24 UTC in reply to "Comment by dayalsoap"
evert Member since:

If you're on Vista / Win7, you can choose to NOT install GRUB in MBR, but on the Linux partition itself. Then, use EasyBCD:

You might be interested in Ubuntu WUBI (does not mess with your partitions).

When GRUB starts, and without a boot menu, you have to fix the GRUB settings from within Linux. If you install a newer distro, chances are that you get GRUB2, which is horrible to configure.

Again, when you install the boot manager (GRUB) into the Linux partition (NOT in the MBR), than you can change the active partition using fdisk or other partitioning programs. The active partition is the one that will boot. Some small boot loaders use this on startup so you can choose which partition to start.
My personal favorite is SBM (smart boot manager):

Reply Score: 4

RE: Comment by dayalsoap
by gilboa on Wed 19th May 2010 08:20 UTC in reply to "Comment by dayalsoap"
gilboa Member since:

I'm newer to Linux. How would one boot to Windows without the boot menu?

As far as I remember the problem was not a missing boot menu - but zero timeout during which you can choose what OS (Fedora, Windows) to boot.
By default, Fedora installer was supposed to detect that there is an existing installation, and automatically put the non-zero menu display time.

Anyone hit by this bug, could simply boot into Linux, edit the /etc/grub.conf file, and replace the timeout=0 with timeout=<insert_your_preferred_timeout_here>.

- Gilboa

Edited 2010-05-19 08:22 UTC

Reply Score: 3

RE[2]: Comment by dayalsoap
by Rahul on Wed 19th May 2010 22:25 UTC in reply to "RE: Comment by dayalsoap"
Rahul Member since:

I was the one who filed the bug report. Actually, you can just press the shift key during bootup and it would show up the menu.

Reply Score: 2

not a grub bug
by r0b0 on Wed 19th May 2010 09:06 UTC
Member since:

...also I wouldn't call this a "grub bug". It is an installer bug creating suboptimal grub configuration.

Reply Score: 4

by pabloski on Wed 19th May 2010 16:16 UTC
Member since:

This is the same bug ubuntu 10.04 had just before releasing.

I think this is a new feature in the linux systems "The Kill Windows" switch ;)

Reply Score: 1

Grub bug
by marktn on Thu 20th May 2010 00:54 UTC
Member since:

I hit this bug when testing the latest Fedora release (assuming it was Beta...). Where the bug is particularly annoying is for those of us who dual-boot and set the other OS (in my case, windows 7) as the default. At first I thought Fedora failed to install.

Reply Score: 1