On Tuesday, 12 November 2019 17:40:13 UTC, Charles Peters wrote: > > ... > You can reinstall grub to the master boot loader using the OS which > originally controlled grub, (ie, something like grub-install /dev/sda". then > regenerate the grub menu with "update-grub". Or you can modify the grub > settings in qubes to provide the menus you want. > > This does not work, because the standard Linux grub-install and grub-update commands rely on the existence of grub.cfg to pick up each target system.
The way I "solved" it was to leave the machine booting into grub by defualt, but to bring up the boot menu when I wanted Qubes. This has a slight security-by-obscurity advantage in that it is good for demonstrating that this is a fully working system, witout making the presence of Qubes obvious to a casual check. However, as with all s-by-obs its no defence against expert opposition! I continue to seek a full solution, especially as one of my machines refuses to bring up the boot menu: manufacturer advice is to select an alternative boot target before closing down windows 10. Happily my machine has not had W 10 since half an hour after I unboxed it... and that is the hidden flaw (for some hardware systems) with Rafael's suggestion. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2b802b90-3f25-4bce-b31f-a1c7a8760446%40googlegroups.com.
