Thanks Kevin,

   That helped some, but I still would like to know how to boot into the new kernel instead of the old one.

  Thanks

   FrankM

Kevin Brown wrote:

> Funny.  I just happened to bookmark a grub mini-howto that describes just this
> situation:
>
> Linux
> Win98
> Win2k
>
> http://www.linuxdoc.org/HOWTO/mini/Multiboot-with-GRUB.html
>
> > Hi Group,
> >
> >   I need a little help with my boot loader.
> >
> >   History: I installed RH Linux 7.0 some time ago with Lilo as my boot
> > loader. I had no problem loading either win2k or Linux, each on their
> > own HD. I just selected Linux or DOS and away I went.
> >
> >                   Then I upgraded to RH 7.1 and after that 7.2. This ia
> > where my problem started. I choose Grub as my loader and I managed to
> > totally mess up my MBR. After some thinking I did a fdisk /mbr and was
> > able to reinstall win2k and get my mbr back, but only for win2k.
> >
> >                    Now I load linux with a boot floppy, works fine,
> > however, I used RHN up2date to upgrade my kernel from 2.4.7-10 to
> > 2.4.9-31, all went OK according to the messages. I rebooted, ran uname
> > -a and , low and behold my version # is still 2.4.7-10.
> >
> >                    Looking at my numerous boot configuration files I see
> > that the new kernel is included, but does not boot.
> >
> >                    My question is this: How do get my new kernel to
> > boot, and all my O/S's to load from the HD, I have win98. win2k and RH
> > 7.2. I also need to know how I find out what .conf file my system uses
> > to load, I am still booting linux from a floppy, and which .conf files
> > can I get rif of, if any.
> >
> >                     Any help is greatly appreciated.
> >
> >                     Thanks
> >
> >                      FrankM
> >
> > ==================================================
> >
> > ## This is my grub.conf
> > # grub.conf generated by anaconda
> > #
> > # Note that you do not have to rerun grub after making changes to this
> > file
> > # NOTICE:  You do not have a /boot partition.  This means that
> > #          all kernel and initrd paths are relative to /, eg.
> > #          root (hd1,0)
> > #          kernel /boot/vmlinuz-version ro root=/dev/hdb1
> > #          initrd /boot/initrd-version.img
> > #boot=/dev/hdb1
> > default=2
> > timeout=10
> > splashimage=(hd1,0)/boot/grub/splash.xpm.gz
> > title Red Hat Linux (2.4.9-31)
> >  root (hd1,0)
> >  kernel /boot/vmlinuz-2.4.9-31 ro root=/dev/hdb1
> >  initrd /boot/initrd-2.4.9-31.img
> > title Red Hat Linux (2.4.7-10)
> >  root (hd1,0)
> >  kernel /boot/vmlinuz-2.4.7-10 ro root=/dev/hdb1
> >  initrd /boot/initrd-2.4.7-10.img
> > title DOS
> >  rootnoverify (hd0,0)
> >  chainloader +1
> >
> > ==========================================================
> >
> > ##This is my lilo.conf.up2date-1017508141.67 file
> > prompt
> > timeout=50
> > default=DOS
> > boot=/dev/hdb1
> > map=/boot/map
> > install=/boot/boot.b
> > message=/boot/message
> > linear
> >
> > image=/boot/vmlinuz-2.4.7-10
> >  label=linux
> >  initrd=/boot/initrd-2.4.7-10.img
> >  read-only
> >  root=/dev/hdb1
> >
> > other=/dev/hda1
> >  optional
> >  label=DOS
> >
> > ===========================================================
> >
> > ## This is my lilo.conf file
> > prompt
> > timeout=50
> > default=DOS
> > boot=/dev/hdb1
> > map=/boot/map
> > install=/boot/boot.b
> > message=/boot/message
> > linear
> >
> > image=/boot/vmlinuz-2.4.7-10
> >  label=linux.bak
> >  initrd=/boot/initrd-2.4.7-10.img
> >  read-only
> >  root=/dev/hdb1
> >
> > other=/dev/hda1
> >  optional
> >  label=DOS
> >
> > image=/boot/vmlinuz-2.4.9-31
> >  label=linux
> >  root=/dev/hdb1
> >  read-only
> >  initrd=/boot/initrd-2.4.9-31.img
> >
> > =============================================================