Subject: Re: bin/20200: Let etcupdate skip files with strictly local modifications (patch)
To: None <firstname.lastname@example.org>
From: David Laight <email@example.com>
Date: 02/04/2003 10:32:58
> Let etcupdate skip files with strictly local modifications (patch)
I had a similar thought about the postinstall script - which does a
similar job in a different way.
This was after I'd used 'build.sh instal=xxx' to populate a filesystem
for a netbooting client and found almost all of /etc missing.
It seemed to me that you needed to know the file that the user
had started with. Then you can tell whether there are any local
modifications, if not it is (probably) safe to install the new
version of the file.
If the master file has changed, and the user has added local config
stuff, then the user (probably) needs to fix his file to incorporate
the standard changes. Something like the CVS diff merging code
might actually work - especially if there are no conficts.
However as a 'stage 1' I considered requiring the date on the
users file to be newer than the one being installed (ie the user
has edited it) in order to pass the postinstall checks.
This does require that the issue files for /etc be kept somewhere
on the target system. /etc/.issue/* could be used.
David Laight: firstname.lastname@example.org