I have also seen this with grub2. For example, grub2 will create 4 entries for booting Slackware, one for each kernel in Slackware's boot directory.
The only way I know of to prevent this is to:
1. First, add this line to the
/etc/default/grub file:
GRUB_DISABLE_OS_PROBER=true. This will prevent grub2 from adding other operating systems to your grub menu.
See this section of the Ubuntu grub2 tutorial:
https://help.ubuntu.com/community/Gr...b%20%28file%29
2. Then you need to create custom boot entries for the operating systems that you want to be included in your grub menu. To do that you need to add custom menu entries in the
/etc/grub.d/ directory. To do that see this:
https://help.ubuntu.com/community/Gr...Menu%20Entries
That whole tutorial is a good introduction to grub2.
For reference, here is my custom boot entry in /etc/grub.d/ for booting Slackware's generic-smp kernel:
Code:
menuentry "Slackware32-13.1 on /dev/sda5" {
set root=(hd0,5)
linux /boot/vmlinuz-generic-smp-2.6.33.4-smp root=/dev/sda5 ro
initrd /boot/initrd.gz
}
Remember to run:
after making any changes to grub2 config files or after adding custom entries.
The only other option would be to remove unwanted entries from
/boot/grub/grub.cfg. Note that this file says you are not supposed to edit it. It
can be edited though. But the problem is that whenever Ubuntu updates it's kernel (which is often) the file will be overwritten and all of your edits will be replaced and you will need to edit the file again.
Custom boot entries in /etc/grub.d/ will persist after kernel updates.
I hope this has not confused you too much. Write back if you need more help.
If anyone else out there knows a better way to do this I would love to hear it.
I have not used the Super Grub Disc for quite some time, since I know to control grub2 myself. I do not know if the Super Grub Disc has any options for this.
