Well, first of all thanks a lot to all of you guys for your interest and your replies.
bw123 wrote:Are you sharing a /boot partition with several distros or something?
Huh? Hmm no, that can't be... unless... maybe I selected the whole disk instead of a partition when I was asked where I wanted /boot to be? Maybe I made that mistake? Perhaps. Maybe the whole disk was the default place for /boot in both Manjaro and Debian installers, and I had simply left it where it was. Maybe I'm wrong. I thought each distro's partition was it's own /boot.
milomak wrote:i don't think any distro forces you to run grub during the installation process

THIS is what I was looking for! I wasn't sure if Debian installer actually had such an option or not. I was messing with Mint 19's installer and I couldn't get anything like that. So, currently Linux Mint does force you to install it's own GRUB. I'm making a thread at their forums.
https://forums.linuxmint.com/viewtopic. ... 6&t=283455Head_on_a_Stick wrote:The trick is to leave all of the checkboxes for all of the partitions unchecked, then you will see the confirmation screen posted by @milomak.
So, that's the trick... I see, I will try it later.
stevepusser wrote:The GRUB update in Stretch did ask a few questions it, including about whether and where the user wanted to install it--why is the OP skipping over what they did during the upgrade? Surely they told it to install GRUB and this is the root of their problem.
Of course I had to install GRUB when I installed Debian the first time on this machine, it was the only way it could boot. (how could I boot it otheriwse? Debian was alone the only O.S. at a certain point in that machine. About upgrading, I don't know. All I know is that I saw that there was an update for Debian, so I booted my machine, saw the notification in the panel, opened the Discover software and clicked "update". Internet is quite slow in my country. it took it's time to update. When it finished I rebooted, Debian appeared to be fine, but it was strange to see that the custom GRUB theme I had installed from Manjaro was gone and Debian's GRUB theme was back, so I rebooted from Debian and tried to boot into Manjaro just to get a Kernel Panic and nothing else. Later I found out that the Manjaro's recovery mode is still capable of booting Manjaro in that machine. Maybe if I update Manjaro's Grub the way I usually do when I change a theme
- Code: Select all
# grub-mkconfig -o /boot/grub/grub.cfg
But I will still need to remove one of the GRUBs if I don't want to reinstall everything from scratch.
bw123 wrote:I have two debian installs on this machine, but only one has grub installed to avoid confusion, you can just purge it if you don't want it. Be sure and install the ver from the distro you want first!! and you will have to make sure it either probes for debian or has a 40-custom file like debian does to add it to the boot menu.
If this is possible it would be great. How do I purge one of the GRUBs leaving the other one intact?
Ok. I have installed Boot-info-script via synaptics package manager. But... how do you turn this on?
- Code: Select all
# sudo boot-info-script
or
- Code: Select all
# sudo boot_info_script
both say
command not found!
hmm... maybe
- Code: Select all
# sudo apt-get install boot-info-script
Ah... nope. It says the latest version is already installed... what is going on here?