[89] in Back_Bay_LISA
October BBlisa Notes (finally)
daemon@ATHENA.MIT.EDU (Noah Friedman)
Sun Nov 22 17:41:13 1992
Date: Sun, 22 Nov 92 16:52:37 est
From: friedman@gnu.ai.mit.edu (Noah Friedman)
To: John_Rouillard@dl5000.bc.edu
Cc: bblisa@inset.com
Reply-To: friedman@gnu.ai.mit.edu
In-Reply-To: <199211221939.AA19095@dl5000.bc.edu> (John_Rouillard@dl5000.bc.edu)
There are a couple of innacuracies with respect to the summary for GNU tar.
>The current dump scripts provided with gnu tar don't provide for tape
>labels
On the contrary, each volume on the tape has a label indicating
the date, host, filesystem, whether it's a full or incremental dump, and
what tape number in the dump it is.
>There is one bug with the current GNU tar version. The option that
>resets the access time in the inode also resets the ctime which gnu
>tar uses to determine if a file should be dumps.
This isn't so much a bug in tar as it is a feature of unix filesystems.
Open or read on a file will change the atime, and changing the atime back
must update the ctime. You want to avoid using --atime-preserve until mib
finishes implementing the icky kludge he discussed at the talk. (in an
ideal world I would suggest that unix have an "archive time" field in the
inode which could be updated instead of the ctime).
>Dump Support:
> ...
> Operates in parallel? No
This is something else we're working on. :-)
It's already quite trivial to do it, actually... you keep multiple
configuration files and start the dump scripts in parallel.
--
Send mail for the `bblisa' mailing list to `bblisa@inset.com'.
Mail administrative requests to `bblisa-request@inset.com'.
