On Fri, Jul 08, 2005 at 11:03:34PM +0200, Stefan G. Weichinger wrote:
> 
> Gene:
> 
> >>>To me, the obvious cure would be to remove the partial file
> 
> Frank:
> 
> >>This seems dangerous to me. 
> 
> >> It seems easier and safer to to just have amverify buffer the
> >>error and if it is successful in reading the DLE from the next
> >>tape don't output the error.
> 
> Gene:
> 
> >Which makes perfect sense to me.  And, it shouldn't take more than say 
> >10-15 lines of code to do it.
> 
> I agree that this should be solved in amverify(run).
> I really like the idea of limiting write-access to (v)tapes to amdump.
> 
> After the dumps have been done, successfully or hitting EOT, the rest 
> should be read-only and errors covered by the binaries accessing the 
> (v)tapes.
> 
> Following this principle seems to reduce risk to me.

Particularly as (to my knowledge) amverify does no tape writing at
the present time.  It would add an entire new, major set of routines.
-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)