SuSEconfig 4 newbies
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? TIA Pam (refugee from Caldera)
--- Pam R
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?
TIA Pam (refugee from Caldera)
Pam, I am new SuSE user too (refugee from Mandrake!) but I'll take a stab at this (and hope that one of the smart people on this list will correct me if I'm wrong!). I believe SuSEconfig is a script that updates variables, settings etc. whenever you run YaST2 (the update utility). In other words, if you run YaST2, you will see SuSEconfig run automatically at the end. However, if you, for example, download and install a rpm yourself (say, the new mozilla rpm), you will need to run SuSEconfig manually to make sure those global changes are done. The way to do that is to su to root and run: /sbin/SuSEconfig. HTH Cheers, Charles __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
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
On Thu, Jun 06, 2002 at 03:47:01PM -0400, Keith Winston wrote:
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.
Actually, you know, this exact quote should be in the FAQs... Having been 'raised' in SuSE I'm pretty well used to having to tell SuSEconfig to leave 'whatever' alone, but precisely the people who migrate from other Linux/Un*x are bound to get bit by this at some point. mho Jon Clausen
Lourens replying to Pam R
participants (5)
-
Charles Griffin -
Jon Clausen -
Keith Winston -
Lourens Steenkamp -
Pam R