Comment 3 for bug 2027676

Daniel, thank you for reply! I'm really happy to tell you that after

" grub2-probe --target=device --device-map=/dev/stdin /boot/grub2 "
replacement of MKDEVICEMAP_CMD 's default
" grub-mkdevicemap --device-map=/dev/stdout "

- the grub-customizer 5.2.3 runs successfully on my CentOS 8, and populates the GRUB boot menu both with CentOS 8 entries and also the entries from another HDD ;-) Although, before this success I also had to overcome a few filepath errors during grub-customizer operation by making these symbolic links:

cd /usr/bin/ && sudo ln -s ./grub2-mkfont ./grub-mkfont
cd /usr/sbin/ && sudo ln -s ./grub2-mkconfig ./grub-mkconfig
cd /usr/sbin/ && sudo ln -s ./grub2-install ./grub-install
cd /boot/ && sudo ln -s ./grub2/ ./grub

That's despite I've been using all grub2 variables as above at "Grub Customizer environment setup". So it seems that grub-customizer has a few hardcoded values in its' source code, which should be replaced with using these variables to avoid such problems.

Daniel, thank you so much for the excellent software which helps to save a lot of time for GRUB configuration. Please help it walk one last inch to become compatible with modern systems other than Ubuntu (don't know why they preserve grub-mkdevicemap at Ubuntu's grub2, this only cover-ups a problem)