8<
> > Debian rather than Suse, but I had trouble with an upgrade involving
> > grub where I had the old grub installed in the MBR so it was picking
> > up my old menu.lst configuration instead of the new grub.cfg.
>
> Are you saying that in the new grub menu.lst is replaced with grub.cfg?
It is in Debian. The Debian system has a transition state which is to
chain-load grub2 from grub1 by adding an entry to the original
menu.lst. It then invites you to run
/usr/sbin/upgrade-from-grub-legacy to make the grub2 setup 'live' once
you're happy with it.
>
> If so thats going to be messy booting syllable which requires version 0.97 of
> grub as grub 2 will not support the closed source AFS file system.
>
> > I also
> > had trouble with the naming of drives changing which caused great
> > confusion. Could either of those be your problem?
>
> I not sure what you mean there.
> Are you saying that the suse installer might be writing grub to a different
> hard drive?
It wasn't updates to grub, but to other parts of the system, which
made my drives change their names in the system, e.g. hda1 -> sdb1.
Since I had a few non-grub names within the grub config it messed
everything up. If you stick to grub names - like (hd1,2) - then you
SHOULD be OK as long as nothing alters the BIOS discovery sequence,
but I found that using SATA drives on my motherboard interfered with
that too. I have since installed an IDE-SATA converter so that my SATA
drive connects to an IDE port. Yuk.
