Description of problem: After installing RHAS2.1 to one slice of /dev/sda, I
tried installing 8.0 to /dev/sdb for a dual-boot scenario. Anaconda was nice
enough to warn me about not being requested to format /boot, and I proceeded.
I told anaconda to install grub on /dev/sda (where it was after the RHAS2.1
install), and everything was pretty OK.
Except, the stanza for RHAS2.1 was lost when /boot/grub/grub.conf was created.
My enhancement request is to *append* boot stanza if /etc/grub/grub.conf
already exists and you tell anaconda to not format /boot... maybe easier asked
then done, but I'll submit the enhancement request anyway.
You can sort of do this if you a) mount your /boot and b) tell anaconda to not
touch your boot loader config. Because then you'll get grubby updating your
boot loader config and get basically what you want. Not something I'm really
looking at supporting (dual-boot is a definite outlier case)
I'd like to test your assertion/advice here by installing a more current RH
distribution on top of what I have configured now... When you
say "mount /boot", are you saying to switch to VC2 during an install and
physically mount the device outside the realm of anaconda, or just
specify /boot as a filesystem and do NOT format the partition? I certainly
understand the "don't touch the bootloader config" part.
And, if the former, at what point do I mount /boot, and on what specific
directory (/boot, /mnt/sysimage/boot)?
Just specify the partition should be mounted as /boot and don't format the