Bodo Bauer wrote:

YaST won't change any file that has been edited by anyone else. MD5 checksums are stored for each config file YaST (or SuSEconfig) modifies, and the next tine you run it, it will check if there has been modifications since the last run. If so, you'll get a warning and the 'SuSE-version' of the file will be stored in <filename>.SuSEconfig. If want SuSEconfig not to do this, you can either edit SuSEconfig and comment the concernign lines out, or you can set ENABLE_SUSECONFIG (rc.config) to no, which means, that SuSEconfig will not be run by YaST.

Permissions will be reset anyway. To switch this off, set CHECK_PERMISSIONS to 'no' or 'warn'

IŽm not quite sure if YaST really doesnŽt change config files that have been manually edited. We use NIS for name resolving and user authentization. The last line in /etc/passwd has ben set by YaST to "+" but since our NIS-Server uses different shells I changed this to "+::::::/bin/bash" to get the bash when loggin in on the Linux-Box. Unfortunately YaST always changes this back to "+" when running again and does not recognize my modifications. Another thing about YaST and NIS: even though I set the USE_NIS_FOR_RESOLVING flag in rc.config to "yes" YaST does not edit host.conf to include the line "order hosts,nis" as should be expected but leaves it at "order hosts". Thus NIS would not be used for name-resolving. But then again at least here it realizes that this was changed manually and just stores its version in host.conf.SuSEconfig as you described above. Thanx , Mario Oschwald -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e