On an upgrade from an earlier release, people will have /etc/modprobe.d/anaconda which isn't owned by any package.  To avoid spewing warnings, it's probably worth migrating it in the %post of m-i-t.

Something like the following should work (also removes a now unneeded prereq)

[katzj@erebor F-11]$ cvs -q diff -u
Index: module-init-tools.spec
===================================================================
RCS file: /cvs/pkgs/rpms/module-init-tools/F-11/module-init-tools.spec,v
retrieving revision 1.85
diff -u -u -r1.85 module-init-tools.spec
--- module-init-tools.spec      19 Mar 2009 19:11:35 -0000      1.85
+++ module-init-tools.spec      17 Apr 2009 15:00:19 -0000
@@ -12,7 +12,7 @@
 Source4: depmod-dist.conf
 Source5: modprobe-dist-oss.conf
 Exclusiveos: Linux
-Prereq: /sbin/chkconfig sh-utils
+Prereq: sh-utils
 Obsoletes: modutils-devel modutils
 Provides: modutils = %{version}
 BuildPrereq: zlib-devel docbook-utils
@@ -61,7 +61,9 @@
 rm -rf $RPM_BUILD_ROOT
 
 %post
-# Removed 2.4 compatibility in post-F10 (in F11 onwards).
+if [ -f /etc/modprobe.d/anaconda -a ! -f /etc/modprobe.d/anaconda.conf ]; then
+  mv /etc/modprobe.d/anaconda /etc/modprobe.d/anaconda.conf
+fi
 
 %files
 %defattr(-,root,root)