From owner-freebsd-current Sun Oct 11 01:25:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01981 for freebsd-current-outgoing; Sun, 11 Oct 1998 01:25:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01973 for ; Sun, 11 Oct 1998 01:25:26 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA19450; Sun, 11 Oct 1998 18:25:04 +1000 Date: Sun, 11 Oct 1998 18:25:04 +1000 From: Bruce Evans Message-Id: <199810110825.SAA19450@godzilla.zeta.org.au> To: bde@zeta.org.au, mark@grondar.za Subject: Re: /usr/include/sys/cam/scsi... Cc: current@FreeBSD.ORG, garbanzo@hooked.net, perlsta@fs3.ny.genx.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >cd /usr/include; find . -type f -ctime +N -delete >> > >> >Where N (in days) is chosen to be a bit longer than the number of days >> >between now and your last "make world". >> >> Don't do that. Includes are installed by `install -C', so most of them >> should be very old. > >Huh!!?? Why does it work, then? Oops. It does work. `install -C' should attempt to avoid modifying ctimes, since incremental backups should be based on ctimes, so modifying ctimes mainly bloats such backups. I forgot that it doesn't actually avoid modifying them. It always does the following operations on the target file: fchown(), fchmod(), fchflags(); and at least some of these are required to clobber the ctime even when nothing has changed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message