On Thu, Jun 06, 2002 at 08:03:02PM +0100, Pam R wrote:
I've just migrated to SuSE 8.0 and have seen several references in this mailing list to running SuSEconfig after updating. Would some kind soul please explain why SuSEconfig should be run, and when,, and what exactly dies it do?
Welcome to SuSE. SuSEconfig is a system script that runs many other scripts (all named SuSEconfig.xxxx) to update system configuration files (and other things like the dynamic lib cache) for you in an automated way. The main script is /sbin/SuSEconfig and all the helper scripts live in /sbin/conf.d. Look in that directory for all the individual scripts. It is run automatically when you change something in YaST2. You can also run it manually (as root) whenever you change something it should know about or needs to take action on, like if you manually install a library or a package that includes a library. As nice as SuSEconfig is, there are times when I want to manually edit and maintain a file. In this case, you usually have to set a variable in one of the /etc/sysconfig files to tell SuSEconfig to leave your file alone. This bites a lot of newcomers to SuSE when they edit something and then SuSEconfig stomps on it the next time they change something with YaST2. Best Regards, Keith -- LPIC-2, MCSE, N+ Got spam? Get spastic http://spastic.sourceforge.net