I've solved this problem before by configuring a setup which implements the Boot Loader Specification
https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/ I chose to do this by hand maintaining grub.cfg fragment files for each of my systems and including these files in the grub.cfg generated by grub-mkconfig via a custom grub hook. On April 21, 2016 3:00:55 PM EDT, drsmith <[email protected]> wrote: >I'm currently working on installing a server with two logical drives in >it: >sda and sdb. Each logical drive is going to get an installation of >Linux >and each install has a different purpose. The first install is mostly >used >for recovery scenarios while the second would be the production >installation. > >The issue I've run into is that I have two /boot partitions, but the >MBR of >the first disk only points to one grub.conf file. Manually keeping >these >synchronized isn't something I'd like to do if I could avoid it. > >Either I have to have one shared /boot partition that gets mounted by >both >installations or I have to figure out how to get grub to chainload >itself >from the second drive. In the chainload scenario, you would see two >menus >where choosing the install on the second hard drive gives you the menu >for >that installation. > >I've run this through the stack-exchange sites and I've tried many >searches >over the past few days, but information on this seems to be rather >scarce. >Maybe I'm not thinking of a better possibility. Any insight you could >offer would be greatly appreciated. > >Thanks. > > >------------------------------------------------------------------------ > >_______________________________________________ >Help-grub mailing list >[email protected] >https://lists.gnu.org/mailman/listinfo/help-grub
_______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
