Article 6GM2K my 2 distros' installers (and boot repair programs) delete each other's bootloader entries

my 2 distros' installers (and boot repair programs) delete each other's bootloader entries

by
newbiesforever
from LinuxQuestions.org on (#6GM2K)
I had a vexing little problem with the installer on one of my distros, MX. Then I just discovered that another distro I am exploring, Peppermint, causes the same problem when installed.

Each distro's installer is of course theoretically supposed to detect the other distro, and write it into the grub menu; but in practice, they often fail to. I find that MX's installer is unpredictable about this: sometimes it successfully detects the other distro (Peppermint or whatever else I am installing at the time), and sometimes it doesn't. I supposed that was an MX issue, really because normally MX is all I run. (I think I've tried repeatedly re-writing the grub menu, and have observed different results.)

Today, I restarted after installing Peppermint from a liveUSB. To my surprise, the Peppermint installer did the same thing: wrote a grub menu with no entry for my MX installation. I sighed, and ran the MX liveUSB to reinstall MX's bootloader. What else could I do? Unfortunately, it just did the opposite: wrote a new grub menu that left Peppermint out.

So, I guess I can't have both distros. Their installers (or grub re-writing programs) cancel each other out. Any ideas? Um, well, I guess I could manually write the menu, if I want to invest the time, right?
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments