Comment # 38 on bug 1076779 from Michael Chang

> Anyways, another option would be to run the os-prober outside the chroot, ie
> within the installation environment and only inject it's findings into the
> target. Since /etc/grub.d/30_os-prober is quite expensive anyways, I'd favor
> removing that and converting it into some standalone script that can be
> called by e.g. YaST when needed rather than each bootloader update. Not sure
> if that is doable short term though :-)

I agree with you. The only drawback could have is that it changes the behavior
as user intervention is needed to run that standalone script after installation
(in lieu of YaST).

Probably as FATE candidate ?