Fedora :: Prevent Yum Update From Undoing Changes Made To Files In /etc/init.d?

One of my machines is a desktop with a WIFI connection. This machine is not configured to use NetworkManager; instead, it still does things the old way via /etc/sysconfig config files.

Problem: this WIFI connection requires wpa_supplicant. By default, F11 brings up the network at priority 10 and wpa_supplicant at priority 23. So dhclient fails its initial attempt to obtain an IP for wlan0 (it will retry and succeed but by then it's too late). This causes other network-related startup tasks to fail. For example, ntpdate fails. This is problematic for systems with faulty CMOS clock batteries since ntpd will reject updates if the clock skew exceeds some threshhold (so ntpdate is usually used to preset the clock).

The workaround is easy enough: add "Required-Start: wpa_supplicant" dependency to the init stanza in /etc/init.d/network and let chkconfig figure out how to rearrange the priorities. This ensures that wlan0 is actually capable of sending a DHCP request when dhclient starts.

This works fine...until yum update decides to replace the scripts in /etc/init.d and, consequently, things go back to the old, broken startup priorities.

So my question: Can yum be told to not change files in /etc/init.d that have been modified by the administrator? Or to at least not overwrite the LSB-style init stanza in those files?

Alternatively, is there a better way to do this that's not vulnerable to updates? I tried playing with the modprobe.conf "install" option to pre-start wpa_supplicant before wlan0 comes up but that has so far been unsuccessful.