| YouTube Videos |
| FILTERS: |
| ALL |
| Dual Boot MultiBoot |
| Android |
| Android-x86 |
| Backup Cloning |
| Chromecast |
| Linux |
| Messaging IM SMS |
| Misc. Soc Media |
| Music Jazz MPB |
| Remote Controls |
| Screen Recording |
| Smart-TV IPTV |
| USB Flash Drives |
| Windows |
 |
Krister's Blog krister at hallergard dot com | Last Updated: 2018-10-26 Newer version |
|
When generating Grub2 bootmenus, I have now completely stopped using the script /etc/grub.d/30_os-prober, and instead add other operating systems as menuentries in the script /etc/grub.d/40_custom,
as links to the menu files boot.cfg generated by update-grub in /boot/grub/ or /boot/grub2/ of the other operating systems. Alternative kernel command lines are only generated for the system performing
the update-grub with its /etc/grub.d/10_linux script.
This allows jumping between the bootmenus, which is kind of cool. More importantly, the updated kernels can be reached for all the operating systems. With this bootmenu I avoid the problem that Kubuntu and Linux Mint do not pick up the full command lines for openSUSE and Fedora. And I do need the full command line on my PC to include the "iommu=soft" parameter as explained in detail here. The suggestion to use bootmenu links instead of kernel command lines came from Marcin82 - thanks!.  View Video 2 min
|
 /etc/grub.d/40_custom on Kubuntu |
 Linux Mint 18.3 Bootmenu on sda2 |
 Kubuntu 18.04 Bootmenu on sdb6 |
 openSUSE Leap 15.0 Bootmenu on sdb7 |
 Fedora 28 Bootmenu on sdb8 |