On Wed, 5 Dec 2007, Joe Morris (NTM) wrote:-
On 12/05/2007 09:14 PM, David Bolt wrote:
AFAIK, if YaST2 is used to generate a file, in this case /etc/aliases and the original file has been modified by the user, YaST2 saves the file with the changes it's made to a file with the .YaST2save extension.
I believe it is similar to rpmsave files. It is the original file saved with the YaST2save (meaning a backup created by YaST2). Yast does modify the original config file. SuSEconfig similarly does this as well. I do think you are correct though that it only does this when you have edited the file independently of Yast.
A couple of quick tests editing files manually and using YaST2 shows that the YaST2save files are backups of the original. I had it mixed up with the files saved with the .SuSEconfig extension[0]. Those are the files that are saved instead of overwriting any user changes. [0] As discovered when creating my own sendmail.cf files and not telling YaST2/SuSEconfig to not bother creating a copy as well. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys | SUSE 10.1 32bit | openSUSE 10.2 32bit | openSUSE 10.3 32bit SUSE 10.0 64bit | SUSE 10.1 64bit | openSUSE 10.2 64bit | RISC OS 3.11 | RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org