* Lukas Ocilka <lukas.ocilka@suse.cz> [Feb 18. 2011 10:34]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dne 16.2.2011 17:50, Thomas Goettlicher napsal(a):
Le 16/02/2011 17:07, Thomas Goettlicher a écrit :
We want to get rid of the myth that YaST accidentally overwrites files.
it was probably very rare anyway :-). I remember YaST stores a file md5sum somewhere.
That said, what is the prefered action? backup the old file or write some sort of file.ext.yast prefered example? It depends. If YaST can parse the whole configuration file it should only change the affected values and leave the other values untouched. If that isn't
On Wednesday, February 16, 2011 05:33:44 pm jdd wrote: possible I think YaST should warn the user that not all manually edited config options can be preserved.
Sometimes this can still happen - it's actually not YaST fault but configuration-design fault:
If a configuration is generated from sysconfig (/etc/sysconfig/...) and user changes the generated file, YaST doesn't read the changed file but reads/writes sysconfig variables instead. After that, a particular service can rewrite the user-crafted configuration file by using values from sysconfig.
Thats the magig "SuSEconfig" which should not touch the file if it was changed by a user. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org