From bb@suse.com Mon Feb 23 22:35:16 1998 From: bb@suse.com To: users@lists.opensuse.org Subject: Re: [S.u.S.E. Linux] Preserving system changes from YaST Date: Mon, 23 Feb 1998 23:35:16 +0100 Message-ID: <6cstj4$1in$1@Galois.suse.de> In-Reply-To: <[S.u.S.E. Linux] Preserving system changes from YaST> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0358914455191366279==" --===============0358914455191366279== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Ted Harding wrote: >=20 > And Hi again! >=20 > The question this time concerns how to preserve manual changes made to syst= em > setup from being re-set by YaST. >=20 > The simplest answer would be to the question: what files are changed when Y= aST > reconfigures the system? Then, I would know what files to keep "backup" cop= ies > of, so that I can then do a "diff" with the new versions created by YaST, > restore changed features I want to keep, and allow the changes which I real= ly > want. 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 .SuSEconfig. If want SuSEconfig not to do this, you can either edit SuSEconfig and comment the=20 concernign lines out, or you can set ENABLE_SUSECONFIG (rc.config) to no,=20 which means, that SuSEconfig will not be run by YaST. Permissions will be reset anyway. To switch this off, set=20 CHECK_PERMISSIONS to 'no' or 'warn' Ciao, BB --=20 Bodo Bauer S.u.S.E., LLC fon +1-510-835 7873=20 bb(a)suse.de 458 Santa Clara Avenue fax +1-510-835 7875 http://www= .suse.com> Oakland CA, 94610 USA -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e --===============0358914455191366279==--