Comment 42 for bug 293139

Description of problem:

The traditional way to provide information which cannot be provided by
DHCP (specifically in my case additional DNS domain names in search path)
has been by writing an /etc/dhclient-exit-hooks script which can be used
to edit the /etc/resolv.conf file after it is created by DHCP. This script
is no longer being run when NetworkManager creates resolv.conf

Version-Release number of selected component (if applicable):

NetworkManager-0.7.0-0.9.3.svn3623.fc9.x86_64

How reproducible:

Every time I boot.

Steps to Reproduce:
1. Boot system, observe NetworkManager generated resolv.conf does not
   have the changed dhclient-exit-hooks would have made.

Actual results:

see above

Expected results:

augmented search path in resolv.conf

Additional info:

I'd be happy to learn the "new way" to achieve the same thing
dhclient-exit-hooks did, but on the other hand, I'd really wonder
why there would need to be a "new way" other than obsessive OCD
on the part of developers. How hard is it to just run the dadgum
script if it exists?