I was just a bit quick with the fingers. I used yast1 in 7.0 and edited nameserver configuration. as it started to run the usual scripts after commiting to the change I noticed I had made a mistake and I killed yast. I thought I killed it before any scripts ran. I restarted yast and went back into nameserver configuration. I then commited again and it said "another suse config is running. waiting for it to finish......." I checked 'ps ax' and it was true. the thing was still running. I killed it and then closed my other yast session. I opened it again. I had no resolv.conf anymore. I edited nameservers again and tried to commit but it won't start suseconfig in yast anymore. I tried to hand start suseconfig but it won't start anymore saying it detected a running copy even though there is none. I know this is all my fault just saying what happened and there should be some recourse of action. mk _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com