4.2BSD restore(8)

[Rick Lindsley]

In article <1631 at wucs.UUCP> nz at wucs.UUCP (Neal Ziring) writes:
> 
> In fact, this problem is due to a quirk in a dump/restore, the
> restored files have the correct modification time, but their creation
> times are the time of the restore!
> 

As previously discussed, 4.2 & 4.3 restore do not use the raw disk, so
they cannot maintain the ctime on the files. But changing dump to not
look at the ctime could bite you in a big way -- ctime is changed if
the owner, group, or mode was changed. Looking at the mtime will
guarantee that you have a correct *copy* of the binary, but it may not
be the correct owner, group, or mode! Also, if you link two files together,
the new link won't appear on your dump because changing the link count
changes the ctime, not the mtime.

And of course, the reasons for doing a level 0 dump after a restore have
also been expounded upon in this space.

Rick