Allegedly, on or about 15 February 2016, Mike Wright sent: > I have several large disks filled with experiments and multiboots... Once you sort this out, you want to plan how you do multiboots in the future. Way back when I tried it, and even two is a pain, one good solution was to make your own custom boot partition, and all it did was let you select which partition to boot, it chainloaded the next one. Whatever the /next/ one was, is a Fedora install with its own boot partition. Whenever that installation does any kernel updates, it only touches files in its own /boot. Likewise, the alternative /next/ thing to boot, was a CentOS install, with its own boot partition. And whenever it does any kernel updates, it only messes with file in its own /boot. I treated new installations as if they were a complete new hard drive to themselves, whether that's actually the case (and dedicating a whole drive to an OS tends to be easier), or whether I was halving a drive between two OSs, but still acting as if each OS was the only drive in the box. Other people eschew multibooting for running virtual machines. In essence, you have a container that pretends its the hard drive for a machine. Everything that instance does to itself, is all within that container. I've since reclaimed my sanity by not multibooting. I use more than one computer. Much more precise division between things that way. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 Boilerplate: All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I only get to see the messages posted to the mailing list. ZNQR LBH YBBX! -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org