Preupgrade behavior or bug?
csava at central.ucv.ro
Tue Jan 26 11:01:38 UTC 2010
On Tue, 2010-01-26 at 11:48 +0100, Thomas Janssen wrote:
> 2010/1/26 Cristian Sava <csava at central.ucv.ro>:
> > On Tue, 2010-01-26 at 11:08 +0100, Thomas Janssen wrote:
> >> 2010/1/26 Cristian Sava <csava at central.ucv.ro>:
> >> > Hi all,
> >> > I usually manually upgrade my fedora systems but tried using preupgrade
> >> > in multiboot configurations.
> >> > If windows is the boot manager ...
> >> > Why update configuration in preupgrade change the boot flag, leaving an
> >> > unbootable system or with other boot order?
> >> > Sure, it's easy fixable but not desirable.
> >> > So why?
> >> How is preupgrade supposed to change the windows bootloader? If you
> >> think you have to use the windows bootloader, you have to fix it every
> >> update/upgrade
> >> --
> >> LG Thomas
> >> Dubium sapientiae initium
> > By the way,
> > Do you understand what the boot flag is and for what?
> > Hint: "fdisk /dev/sda" and toggle boot flag.
> > So why to change this on upgrading in some environments?
> Preupgrade never changed a boot flag here. And i have "some"
> environments. What i do not have is a windows and i would never use
> the windows bootloader. But to each their own. So, what are you doing,
> or with other words, what's so special in your environment? Playing
> around with bootorder in bios to workaround some mess?
> LG Thomas
> Dubium sapientiae initium
Take a simple dual boot windows XP and fedora system booted by windows,
xp on sda1 and linux on sda2 - boot flag on MBR, so on sda.
After upgrading the boot flag is on sda2. Why?
This even happen when upgrading using install disks (I just tested it).
So why this?
More information about the test