After following Harald's excellent fixes for the broken dracut, I noticed that I have possible 'left overs' in /etc/udev/rules.d/ on my "continuously updated Rawhide system" :

[tbl@tlondon rules.d]$ ls -l /etc/udev/rules.d/ total 32 -rw-r--r--. 1 root root 1357 Jan 19 07:26 51-android.rules -rw-r--r--. 1 root root 55 Jan 14 16:49 60-sysprof.rules -rw-r--r--. 1 root root 254 Jul 9 05:51 70-luks.rules -rw-r--r--. 1 root root 788 Dec 24 2009 70-persistent-cd.rules -rw-r--r--. 1 root root 629 Dec 24 2009 70-persistent-net.rules -rw-r--r--. 1 root root 205 Feb 9 2011 80-podsleuth.rules -rw-r--r--. 1 root root 987 Jul 9 05:51 99-resume.rules -rw-r--r--. 1 root root 749 Jul 9 05:51 99-root.rules [tbl@tlondon rules.d]$

'rpm -qif *' reports that 60-sysprof.rules belongs to sysprof-1.1.8-3.fc17.x86_64, that 80-podsleuth.rules belongs to podsleuth-0.6.7-14.fc15.x86_64 and that the other files are 'unowned'.

From the dates, I'm guessing I missed cleaning up 70-luks.rules,

99-resume.rules and 99-root.rules.

Checking a freshly installed FC17 VM install, I see only 60-fprint-autosuspend.rules and 90-alsa-tools-firmware.rules installed.

Believe 51-android-rules is from installing/using android-tools, so that leaves the very, very old 70-persistent-cd.rules and 70-persistent-net.rules.

Safe to clean these? Any reasons for keeping these around?

Anything missing?

Thanks, tom