Description of Problem:
neat doesn't start if /etc/resolv.conf is absent. Its's bad behavior, because
somebody may try to use neat to create missed /etc/resolv.conf
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mv /etc/resolv.conf /etc/resolv.conf.badneat
2. start neat
neat will show traceback output and fall down
neat must start with proposition to create missed /etc/resolv.conf
the same in 7.3
Created attachment 65465 [details]
Fixed in CVS.
Fix confirmed with redhat-config-network-1.1.12-1.