Karl Larsen wrote:
John Austin wrote:
On Sun, 2007-11-18 at 12:45 +0000, Garry Harthill wrote:
On 18/11/2007, Karl Larsen <k5di@xxxxxxxxxx> wrote:
Timothy Murphy wrote:
Karl Larsen wrote:
Notice f8 has already got a new kernel and it was properly added to
grub. This would not happen if the above was just added to the main
grub.conf.
Why not?
I don't see anything special about your setup.
Most people just have one grub.conf and this seems to work fine.
It works fine if you are not getting upgraded kernel's. I prefer to
use this method because it is open ended. I can add more systems easy.
--
Karl F. Larsen, AKA K5DI
Linux User
#450462 http://counter.li.org.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
What the hell are you driveling on about?
With great caution I agree with Karl here !!!!
It is neater to use chainloader +1 if you have several different installs
When you update the "chained" kernel the "chained" grub.conf is
updated automatically.
On one machine I have a "production" F7 and "development" F7 and F8s
I do not have to play with grub.conf on /dev/sda1
title F7 pagham (2.6.23.1-10.fc7)
root (hd0,0)
kernel /vmlinuz-2.6.23.1-10.fc7 ro root=LABEL=/root_pagham
initrd /initrd-2.6.23.1-10.fc7.img
title F7 Indirect boot of harddisk
root (hd0,4)
chainloader +1
title F8 Indirect boot of fuerte
root (hd0,5)
chainloader +1
John
Thanks John, I may have learned the method from one of your messages :-)
All I said ws I use it and it works fine.
Maybe it's not politically correct but I am using the oldish Boot Manager from
IBM and let it boot whatever OS I have on my system. All OSes are completely
isolated from one another, so I don't see these grub/kernel problems at all.
--
Erik.
