Xref: utzoo comp.unix.wizards:6661 comp.sys.dec:543
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!umd5!trantor.umd.edu!chris
From: chris@trantor.umd.edu (Chris Torek)
Newsgroups: comp.unix.wizards,comp.sys.dec
Subject: Re: bug report etiquette
Message-ID: <2346@umd5.umd.edu>
Date: 24 Feb 88 05:10:56 GMT
References: <2323@umd5.umd.edu> <10102@ulysses.homer.nj.att.com> <2338@umd5.umd.edu> <10110@ulysses.homer.nj.att.com>
Sender: ris@umd5.umd.edu
Reply-To: chris@trantor.umd.edu (Chris Torek)
Organization: University of Maryland, College Park
Lines: 40

In article <10110@ulysses.homer.nj.att.com> ggs@ulysses.homer.nj.att.com
(Griff Smith) writes:
>If [I] had looked in your archives of comp.bugs.4bsd you would have
>found the report of this "nice bug"; I sent it to Berkeley on August
>11, 1987 and also filed to netnews.

Unfortunately, my archives (such as they are) are on those tapes we
have been having trouble reading.  You did indeed post such a fix;
I found it elsewhere since.  And as you mention, that bug was introduced
at Berkeley by A. Nonymous anyway.

[much deleted; see the previous article]

>It would have been an act of simple courtesy to have asked me in
>private communication first.

(That presupposes I would know where to ask.)

>...  I particularly resent having my sentence "I posted
>fixes to comp.bugs.4bsd for the bugs that I found" removed from the
>above followup to my followup.  This twisted the reply to say "your
>driver does too have bugs - look at this juicy one".

I did not mean to do that.  (For that matter, I know of no one who
uses cooked /dev/mt devices anyway.  Without a way to set the block
size, and given the repositioning error on 9 track tapes, what good
*are* block tape devices?  They make terrible disk drives.  Hence a
bug in the block code is hardly juicy.)

At any rate, to get to the point (yes, there is one here), I had
actually intended my previous followup as an apology.  I just like
having the last word :-) and was not careful about the wording of
said words.  Consider this another attempt.

By the way, we have concluded that the problem is in hardware.  A
handy nearby 6250 bpi drive is now successfully reading those tapes,
and we have a call in to DEC to get the TU78 fixed.
-- 
In-Real-Life: Chris Torek, Univ of MD Computer Science, +1 301 454 7163
(hiding out on trantor.umd.edu until mimsy is reassembled in its new home)
Domain: chris@mimsy.umd.edu		Path: not easily reachable