Slashdot Mirror

← Back to Stories (view on slashdot.org)

Fedora Core Doesn't Like to Dual Boot?

Posted by CmdrTaco on from the nobody-noticed-that? dept.

schwatoo writes "It seems Fedora Core doesn't like to boot alongside Windows 2K or XP. According to a bug first reported in February on Fedora's bugzilla site it has a tendency to chew up partition maps making it impossible to dual boot into Windows. No one seems to know quite what is causing the problem and a lot of people are ending up with unbootable machines."

3 of 608 comments (clear)

  1. Re:Now by lazy_arabica · · Score: 5, Insightful
    if this was a Microsoft problem the amount of bitching and conspiracy theories would never end. Lets see how it plays out.
    Stop trolling, and let people speak. I am bored of Microsoft / Linux zealots bashing each other before they even post.

    By the way, there is a Microsoft problem, as the Windows installer destroys the MBR where lilo/grub is usually installed - at least, it was true in win2k and XP. And I didn't see any slashdot story about that.
  2. Here's your trouble... by MsGeek · · Score: 5, Insightful
    This article has more info:
    http://mailman.linux-thinkpad.org/pipermail/linux- thinkpad/2004-May/017754.html

    Here's a quick executive summary for those who don't want to read the thread:
    Linux 2.6 kernels started to report bogus disk geometries thus some unadjusted partitioning tools create bad partition table resulting unbootable Windows.

    --
    Knowledge is power. Knowledge shared is power multiplied.
  3. Re:Now by Graftweed · · Score: 5, Insightful

    Before installing Fedora everything's fine, after installing it people lose the ability to boot into windows. It's as simple as this really. How can you expect linux to take over the desktop with the kind of attitude you just displayed?

    Yes, MS is partly to blame, but joe user won't give a rat's ass about the finer points of booting operating systems, he'll just (quite rightly) blame fedora and be done with it.

    Furthermore this is a bug that's been around for a few months, even before the release of Core 2 so there's really no excuse for this sort of thing. If you're designing an OS to run alongside others it's your responsibility to make sure it doesn't break anything, even if the others are broken somehow.

    Please don't tell me 'Oh, but MS doesn't do this!', that's really no excuse is it?