Prevent F18 anaconda from overwriting bootloader

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================

-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test



[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux