2:49 a.m.
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?
Cristian Sava
4:08 a.m.
2010/1/26 Cristian Sava <csava(a)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
4:19 a.m.
On Tue, 2010-01-26 at 11:08 +0100, Thomas Janssen wrote:
2010/1/26 Cristian Sava <csava(a)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
The bootloader is untuched but the boot flag is. Yes, it
is!
Test it and you will see.
Cristian Sava
4:31 a.m.
On Tue, 2010-01-26 at 11:08 +0100, Thomas Janssen wrote:
2010/1/26 Cristian Sava <csava(a)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?
Cristian Sava
4:48 a.m.
2010/1/26 Cristian Sava <csava(a)central.ucv.ro>:
On Tue, 2010-01-26 at 11:08 +0100, Thomas Janssen wrote:
> 2010/1/26 Cristian Sava <csava(a)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
5:01 a.m.
On Tue, 2010-01-26 at 11:48 +0100, Thomas Janssen wrote:
2010/1/26 Cristian Sava <csava(a)central.ucv.ro>:
> On Tue, 2010-01-26 at 11:08 +0100, Thomas Janssen wrote:
>> 2010/1/26 Cristian Sava <csava(a)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?
Cristian Sava
5:07 a.m.
On Tue, 2010-01-26 at 11:48 +0100, Thomas Janssen wrote:
2010/1/26 Cristian Sava <csava(a)central.ucv.ro>:
> On Tue, 2010-01-26 at 11:08 +0100, Thomas Janssen wrote:
>> 2010/1/26 Cristian Sava <csava(a)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
This also hapen on Windows Vista / Windows 7 and Fedora
10/11/12 on
Intel or Athlon systems (I tested only x32 configurations).
Cristian Sava
5:53 a.m.
Cristian Sava kirjoitti viestissään (lähetysaika tiistai, 26.
tammikuuta 2010):
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?
Because at one point the developers thought it was the right
thing to do. This should be fixed in Rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=533658
--
Markku Kolkka
markku.kolkka(a)iki.fi
6:32 a.m.
On Tue, 2010-01-26 at 13:53 +0200, Markku Kolkka wrote:
Cristian Sava kirjoitti viestissään (lähetysaika tiistai, 26.
tammikuuta 2010):
> 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?
Because at one point the developers thought it was the right
thing to do. This should be fixed in Rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=533658
--
Markku Kolkka
markku.kolkka(a)iki.fi
Thank you very much.
Cristian Sava
5211
days inactive
5211
days old
8 comments
3 participants
participants (3)
-
Cristian Sava -
Markku Kolkka -
Thomas Janssen