Path: utzoo!attcan!uunet!cs.utexas.edu!chinacat!balkan!ssbn!bill
From: bill@ssbn.WLK.COM (Bill Kennedy)
Newsgroups: comp.unix.i386
Subject: Re: BUG in ISC UNIX 2.2
Message-ID: <1600@ssbn.WLK.COM>
Date: 4 Jul 90 20:38:49 GMT
References: <1990Jun30.212356.1209@virtech.uucp> <1990Jul2.155159.664@turnkey.tcc.com> <1990Jul03.002938.14866@virtech.uucp> <44715@ism780c.isc.com> <1990Jul04.120639.9148@balkan.TNT.COM>
Reply-To: bill@ssbn.WLK.COM (Bill Kennedy)
Distribution: na
Organization: W.L. Kennedy Jr. and Associates, Pipe Creek, TX
Lines: 29

:wgb@balkan.tnt.COM (William G. Bunton) writes:
#geoff@ism780c.isc.com (Geoffrey Kimbrough) writes:

#> In article cpcahil@virtech.UUCP (Conor P. Cahill) writes:
#> [ reports problem with our new #!interpreter support ]
#>>
#>>  I don't have any real mechanism to report the bug (that I know of).
#> 	Consider it reported.
:
:Thank you.  Now, when it's fixed, will we all be notified of what "X?"
:disk we should request?
:-- 
:William G. Bunton                                        wgb@balkan.tnt.com
:Tools & Techniques, Inc. Austin, TX        {cs.utexas.edu,uunet}!balkan!wgb

I think that you will have to produce your RESPONSE/ix agreement for
that.  I don't know whether the X? fix will fall under the $675/yr
or $1500+/yr plan but I'm sure that one or the other will do.

Bill raises an interesting point though.  Heretofore, when technical
support was supposedly available we could call someplace and be told
how to get bug fixes.  Not new releases, extensions, or enhancements,
bug fixes.  Now that this is no longer available (unless I misread
Mr. Alcorn's article), how do we find out?  Worse, how does someone
who doesn't read comp.unix.i386 find out?  Does it become part of the
UNIX oral tradition?
-- 
Bill Kennedy  usenet      {texbell,att,cs.utexas.edu,sun!daver}!ssbn!bill
              internet    bill@ssbn.WLK.COM   or attmail!ssbn!bill