Hi, Dan Ritter wrote: > Would downloading the deb packages, then un-ar'ing them in a tmp dir > get you most of what you want?
Maybe. But i was looking for a way to create BIOS+EFI grub-mkrescue ISOs by regular Debian means. To answer my own question: https://tracker.debian.org/media/packages/g/grub2/control-2.06-13deb12u1 says Package: grub-pc-bin ... This package contains GRUB modules that have been built for use with the traditional PC/BIOS architecture. It can be installed in parallel with other flavours, but will not automatically install GRUB as the active boot loader nor automatically update grub.cfg on upgrade unless grub-pc is also installed. ... Package: grub-efi-ia32-bin ... This package contains GRUB modules that have been built for use with the EFI-IA32 architecture, as used by Intel Macs (unless a BIOS interface has been activated). It can be installed in parallel with other flavours, but will not automatically install GRUB as the active boot loader nor automatically update grub.cfg on upgrade unless grub-efi-ia32 is also installed. So yes. They are what i need ... i think ... pinching eyes and crossing fingers ... installed grub-pc-bin. I will see what happens with the next booting. grub-pc-bin suffices for my purpose. In order not to stress my luck, i refrain from installing grub-efi-ia32-bin. (If i find out how to put my EFI into legacy emulation i could probably boot by an installed grub-pc. An i386 EFI startup program and no amd64 EFI startup program would be more problematic.) Now, when i run grub-mkrescue -o output.iso i get an ISO with boot equipment for legacy BIOS and EFI. And with files /boot/grub/locale/ast.mo~ /boot/grub/locale/ca.mo~ ... /boot/grub/locale/zh_TW.mo~ which are useless backup files of their .mo siblings. About 4.3 MB of waste. This is the problem which i wanted to reproduce. Have a nice day :) Thomas
