Linked by Christian Paratschek on Thu 27th May 2004 16:00 UTC
So, there it is, the highly anticipated second release of Fedora Core. Again, I wanted to wait for a few days for things to calm down,and again, I couldn't resist updating my production system within two days after the release. Well, I'm just a Linux junkie, i guess...
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
I got burned by the whole dual-boot bug. I reacted stupidly (panicked), and made it a lot worse. IF YOU HIT THIS BUG, GO READ THE FORUMS BEFORE TRYING *ANYTHING* TO FIX IT. I've also heard about some people having problems with 3rd party bootloaders.
Back to the story...
I thought it was just a bootloader issue, so I reinstalled my old Linux (Libranet). I still couldn't boot Win2K, so I then tried doing a Win2K repair. That didn't work, so I tried reinstalling Win2K (including reformatting the HD). Still didn't work. Tried doing FIXMBR from the Win2K repair console. Still didn't work. After doing some more research, I tried reloading FC2 and following their fix instructions. It still doesn't load. At this point I'm going to try using a drive utility to completely wipe the drive and then try installing Win2K. Hopefully that will fix it. If not, I guess I'm buying a new HD.
From what I've read, the problem is that FC2 corrupts the geometry table of the drive. Linux doesn't use this table, but Windows (2K and XP) does. Do SUSE and Mandrake have this bug? Funny that I haven't heard about it there. Either way, I can't understand why they chose to release with this bug. It was known beforehand and they decided to release anyway. Sure sounds like a blocker to me.