Path: utzoo!attcan!uunet!cs.utexas.edu!csd4.milw.wisc.edu!uxc.cso.uiuc.edu!tank!eecae!netnews.upenn.edu!kings.wharton.upenn.edu!lau From: lau@kings.wharton.upenn.edu (Yan K. Lau) Newsgroups: comp.sys.apollo Subject: Patches (was Re: security hole) Message-ID: <13613@netnews.upenn.edu> Date: 10 Aug 89 13:20:07 GMT References: <44e9d7d4.c4b0@apollo.HP.COM> <511@eda.com> <641@prles2.UUCP> Sender: news@netnews.upenn.edu Reply-To: lau@kings.wharton.upenn.edu (Yan K. Lau) Organization: A Private Heaven Lines: 28 In article <641@prles2.UUCP> collins@nvpna1.UUCP (Donal O Coileain) writes: > >Apollo produces a patch tape every month. In the 9.7 patch tape for JUNE 89 >months before this discussion was started I read : > [deleted] > >You cannot blame Apollo because you don't read the release notes or >understand the bugs/fixes. > What prompted you to get the June patch tape? Do you routinely get patch tapes in case some bug is fix? Usually, I spend time on a problem to the point of not being able to solve it, then call Apollo. It would be nice if I knew something was not *my* problem (rare, it usually is) but a bug in the software. That way I don't waste my time. Without knowing what bugs and fixes exist, we're waiting for a problem to happen when we can prevent it if we knew. We've been through this time and time again. As far as I know, Apollo still does not routinely announce bugs/fixes. That is the problem. Yan. --- Yan K. Lau + the last message of a newgroup will be: )~ + a) longer than one screen & ~/~ lau@scrolls.wharton.upenn.edu + b) something you're not interested in. /\ University of Pennsylvania + your decision, 'n' key or space bar?