Since, to my horror, I've been having a little trouble
matching what ufsrestore finds with what I *thought* ufsdump
was writing to the tape, some *crude* verification would
reassure me:
Maybe after ufsdumping a partition, my .sh-file could have it back up
one tape-position, via:
mt bsf 2 /dev/rmt/0cn ; mt status /dev/rmt/0cn
[quick on-the-fly question: about that "2": is
that very-long-standing requirement to *tell*
"mt bsf" to back up one *more* position than
you really want -- is that a bug, or a
"feature" -- and if a feature, what (fiction)
do they use to *explain* it to someone? ]
and then it would run "ufsrestore -i", and have it do just a single
"ls" before "q-uing" out of it,
...
at which point an
"mt status /dev/rmt/0cn"
should show that the tape had returned to the *same* position it was
when that ufsdump finished -- ie, it's in position for the
*next* ufsdump to be done.
Question: Any idea how I'd code that ufsdump *and the
ufsrestore -i" via the Bourne shell?
(Taking the time to master "expect", for this one optional
verification-use, would be overkill, at least for me.)
Thanks for everything!
David