Subject: Re: sup.netbsd.org now different on -o?
To: Thor Lancelot Simon <tls@mit.edu>
From: Bill Sommerfeld <sommerfeld@orchard.medford.ma.us>
List: current-users
Date: 10/12/1995 20:48:49
-----BEGIN PGP SIGNED MESSAGE-----

> I know that in the past, when I've had to re-get all of NetBSD in stages,
> I've been able to use sup -o to get only the files which differed each
> time, age notwithstanding.  For example, interrupted sup -a invocations
> could be resumed where they left off with -o.  I find that -- contrary
> to my own rather loud advice of last night -- with the current
> sup.netbsd.org, this isn't working; my current sup is regetting everything.
> 
> What's up?  Why the difference?

sup uses the inode-change time to tell if it might need to update the
file modes.

The ctime is the only file timestamp you *can't* update with utime()..

						- Bill

-----BEGIN PGP SIGNATURE-----
Version: 2.6.1

iQCVAwUBMH23bLT+rHlVUGpxAQFGtAQAmmNzLhx4QbDfP3E1p7Dz7QEEI8klKIHv
Xi3rsW1qYiIwKo6gLx/N6C3UAWJM9FuIGusW3SPeOUCjbSeRWQLZ31OfM9ImEjaH
ZLvn89ozS54VFC/r75d5yzubk/VJSwWTsE6igf5kIm4oMUa0VNjR+PIfHFYQ0CCN
hsDZY8+vnb4=
=zfGw
-----END PGP SIGNATURE-----