6 Feb
2006
6 Feb
'06
8:25 a.m.
Eric Dondelinger wrote:
This used to be a problem with *way* old SuSE distributions (until
6.x?). Nowadays, SuSE keeps an checksum of those files that it
generated, and if that checksum no longer matches, the files are not
overwritten.... which can be just as puzzling though, if you actually
*want* to change things using YaST after you first did a manual change.
Moreover, nowadays the configuration is much more modular (config
_directories_ rather than files: /etc/xinetd.d, /etc/apache2/conf.d,
...) so this is even less of an issue.
In the LLL highschools, we modify certain settings manually, and others
via YaST, and we rarely run into problems. But yes, a couple of years
ago, this overwriting of config files used to be a huge problem.
Nowadays it is solved for most cases.
Regards,
Alain
SuSE is
generally not good, if you want to change things yourself.
It is possible too under some circumstances, that Yast owerwrites your
own config when it executes SuSEConfig...
ACK, that's precisely when you edit configuration files directly and don't
tell SuSE / yast not to touch them.