D&C GLug - Home Page

[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]

Re: [LUG] grub WinXP on top

 

kevin wrote:
> Yes changing the Default is correct .......BUT I want it not to happen
> at the Next Kernel update!
> 
> as when Fedora has a new Kernel sometime soon the WinXp will become 2
> the 3 then 4 etc  but I would like it to stay on the top as 0
> 
> 
> 
> On Wed, 2008-12-31 at 14:17 +0000, Paul Sutton wrote:
>> kevin wrote:
>>> Happy New year everyone...
>>>
>>>
>>> Just in case you happen to still be at a PC 
>>>
>>> Does anyone know how to stop a new kernel update from putting it's self
>>> at the top position of the grub Boot menu?
>>>
>>> I have an almost convert from Xp to Linux Dual booting and the Winxp was
>>> Default on Grub at position 0
>>>
>>> but now after a few updates it is as below......... so Linux is 1st to
>>> boot (as it should be ) but not for a WinXp user!
>>>  I know I can remove hiddenmenu.
>>>
>>>
>>>
>>> # grub.conf generated by anaconda
>>> #
>>> # Note that you do not have to rerun grub after making changes to this
>>> file
>>> # NOTICE:  You have a /boot partition.  This means that
>>> #          all kernel and initrd paths are relative to /boot/, eg.
>>> #          root (hd0,0)
>>> #          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
>>> #          initrd /initrd-version.img
>>> #boot=/dev/sda
>>> default=0
>>> timeout=8
>>> splashimage=(hd0,0)/grub/splash.xpm.gz
>>> hiddenmenu
>>> title Fedora (2.6.27.9-73.fc9.i686)
>>>         root (hd0,0)
>>>         kernel /vmlinuz-2.6.27.9-73.fc9.i686 ro
>>> root=/dev/VolGroup00/LogVol00 rhgb quiet
>>>         initrd /initrd-2.6.27.9-73.fc9.i686.img
>>> title WinXP
>>>         rootnoverify (hd1,0)
>>>         map (hd0) (hd1)
>>>         map (hd1) (hd0)
>>>         chainloader +1
>>> title Fedora (2.6.27.7-53.fc9.i686)
>>>         root (hd0,0)
>>>         kernel /vmlinuz-2.6.27.7-53.fc9.i686 ro
>>> root=/dev/VolGroup00/LogVol00 rhgb quiet
>>>         initrd /initrd-2.6.27.7-53.fc9.i686.img
>>> title Fedora (2.6.25.10-86.fc9.i686)
>>>         root (hd0,0)
>>>         kernel /vmlinuz-2.6.25.10-86.fc9.i686 ro
>>> root=UUID=29eaae06-882f-4a65-9b86-e5e617025f7a rhgb quiet
>>>         initrd /initrd-2.6.25.10-86.fc9.i686.img
>>>
>>> Regards
>>>
>>> Kevin Lucas
>>> Minions Post Master(Sub) reprieved (possibly!)
>>> Po House, Minions,
>>> Liskeard Cornwall 
>>> PL14 5LE
>>> 01579363386
>>>
>>>
>>>   
>> Not sure exactly but given the first menu choice is fedora and the 2nd 
>> is winXP,  you have an entry default=0 i would guess this is pointing to 
>> fedora, so therefore making default=1 could make XP boot first,
>>
>> Can anyone help or confirm this
>>
>> Paul
>>
>> -- 
>> Paul Sutton
>> www.zleap.net
>> Support Open file formats ISO 26300 odt
>> Next Linux User Group meet : Jan 3rd : 2pm,  Shoreline Cafe Paignton
>>
>>
> Regards
> 
> Kevin Lucas
> Minions Post Master(Sub) reprieved (possibly!)
> Po House, Minions,
> Liskeard Cornwall 
> PL14 5LE
> 01579363386
> 
> 

Simple answer.
I dual boot a basic XP machine (which wife uses as XP in default
selection)

I adjusted menu.1st in Gnu/Linux (either in SUSE and/or UBUNTU
when triple booting)

a) set time to say 20 seconds to give time to react when you see
GRUB Boot Screen. (default 8 seconds is too fast)

b) set Windows as a choice below the linux options choice
        GRUB NO
e. g.    o      = linux suse
         1      = linux suse  failsafe
         2      = Windows

c) set default  option to "2"  in GRUB entry at top.

When using this a kernal change just alters the linux setting for 0
and 1 leaving Windows alone.

Booting computer sets it to windows by default after 20 seconds in
Grub Screen or on choice in Grub screen.


Regards
Eion MacDonald
No virus found in this outgoing message.
Checked by AVG - http://www.avg.com
Version: 8.0.200 / Virus Database: 270.10.1/1870 - Release Date: 31/12/2008 08:44
-- 
The Mailing List for the Devon & Cornwall LUG
http://mailman.dclug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html