From owner-freebsd-bugs Thu Mar 26 16:06:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17231 for freebsd-bugs-outgoing; Thu, 26 Mar 1998 16:06:21 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17224 for ; Thu, 26 Mar 1998 16:06:16 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA22745; Fri, 27 Mar 1998 11:01:42 +1100 Date: Fri, 27 Mar 1998 11:01:42 +1100 From: Bruce Evans Message-Id: <199803270001.LAA22745@godzilla.zeta.org.au> To: dwmalone@maths.tcd.ie, freebsd-bugs@hub.freebsd.org Subject: Re: bin/6124: Getting md5 to reset access times. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > If you are using md5 to checksum a load of files you probably > > > don't want all the access times changed. This is a small patch > > > which adds a "-r" flag which resets the access times to what > > > they were before the file was checksumed. > > > > I disagree with this change, it doesn't belong in the md5 program. > > Fair enough. > > > cksum(1) and sum(1) doesn't have it either. > > > > mtree(8) and tripwire may need this kind of stuff, but not md5(1). > > Would you be interested in a similar addition to mtree? No, it corrupts the more important inode change times. Mount read-only to avoid corruption of both the access time and the inode change times, not to mention the data. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message