memtest86+ package was shipped without proper installation script adjusted for grub2 until memtest86+-4.20-2. Now there is proper memtest-setup, but it is not run by default as postinstall script. People used to do their own setting at 23_memtest according to numerous web guides. Paths changed in grub2 in F17 in comparison to that of F16, /usr/lib/grub/grub-mkconfig_lib -> /usr/share/grub/grub-mkconfig_lib therefore f17's grub2-install won't accept unpackaged f16's settings and fails to write proper configuration file. In f17 installation, if it was set to update grub, the installation process is aborted after all packages were installed and system doesn't boot any more. It's not fedora's bug, but many people may be in troubles. I think that: either /sbin/memtest-setup should be run as a package postinstall scriptlet or old settings should be detected and removed (chmod -x at least) or path change should be mentioned somewhere (release notes?) just to let people know. Is something like that possible? This happened when updating f16 to f17beta-rc4. Quick fix is to chmod -x 23_memtest, run memtest-setup, run grub2-mkconfig. Better done before installation started. -- --Zdenek Pytela -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
