From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32141 invoked from network); 12 Aug 2004 07:35:46 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 12 Aug 2004 07:35:46 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BvA7l-0001XD-HQ for arch-gentoo-dev@lists.gentoo.org; Thu, 12 Aug 2004 07:35:45 +0000 Received: (qmail 6814 invoked by uid 89); 12 Aug 2004 07:35:45 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 19447 invoked from network); 12 Aug 2004 07:35:44 +0000 Message-ID: Date: Thu, 12 Aug 2004 09:35:44 +0200 From: Radoslaw Stachowiak To: Paul de Vrieze Cc: gentoo-dev@lists.gentoo.org In-Reply-To: <200408112338.13758.pauldv@gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040810104326.GB22751@hydra.joerghoh.de> <200408112303.12503.pauldv@gentoo.org> <200408112338.13758.pauldv@gentoo.org> Subject: Re: [gentoo-dev] small dispatch-conf patch, WAS: extension of etc-update X-Archives-Salt: 68d3ec19-714f-41de-bcd2-db68e3ab4306 X-Archives-Hash: dc9a3593e0601b2be1c310d7612ebc02 > > Because You have to calculate them for all files, and _before_ > > emerge. Also such database has to be regularly updated (sth like > > eupdate/esearch). > > Hmm, I thought that things were only calculated/compared for those > configuration files which might involve updating (those that get ._cfg etc) yes, you are right. i was talking only about CONFIG_PROTECT files. the biggest problem (as I see it) is that it requires special maintenance and overhead to gather this data constantly. of course computational overhead (due to use of md5) is negligible. > > Not that Im sure of time approach, but Could You show one real word > > scenario when ctime/mtime comparison would fail /while md5sum does > > not/ ? > > In cases of clock skew or toying with touch. Esp. the clock skew thing is not > that uncommon. Hmm, good point, but skew must be backwards, and not only it have to be big enough (which is hard to achieve because every second after package installation time, this necessary-for-failure time gap is growing), but it has to be present at the time you hand modify config-file-to-be-lost. i think its almost impossible. Of course ntp time synchronisation would solve this. As to touch. normal touch usage don't put You at risk because file will have mtime > ctime so its not problem. special touch usage (modify mtime to value other than current) is so rare that have to be use for some purpose (eg for mark file to be overwritten by newer update, even ifits modified) which is justified use for me. Files overwritten are backed up by dispatch, so even if sth was screwed up, you can get previous file from dispatch backup. Im going to use it on some machines this month, and will let You know what happened :) -- radek@gentoo.org. -- gentoo-dev@gentoo.org mailing list