Prevent F18 anaconda from overwriting bootloader
Ian Pilcher
arequipeno at gmail.com
Fri Dec 7 21:38:07 UTC 2012
As of "smoke 4" it looks like I am finally able to install Fedora 18
onto a new LV within an existing VG (a VG built from 2 separate software
RAID devices no less)!
I did this in a test VM, and I'm darn glad that I did, because it looks
like it would have trashed the existing (grub "legacy") bootloader
setup on my system. Indeed, the CentOS installation that I "pre-staged"
into the test VM is nowhere to be found in the new Grub menu.
I just ran through the installation workflow again, and I am never asked
where I want the bootloader installed (or if I want it installed at
all).
How can I prevent anaconda from overwriting my existing bootloader?
Thanks!
--
========================================================================
Ian Pilcher arequipeno at gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================
More information about the test
mailing list