Xref: utzoo comp.sys.amiga:41528 comp.sys.amiga.tech:7548
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!hao!hull
From: hull@hao.ucar.edu (Howard Hull)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: A real bug in WB's DISCARD.
Summary: The Locks - Quick! Open the Locks!!!
Keywords: Abandoned Locks GURU
Message-ID: <4696@ncar.ucar.edu>
Date: 12 Oct 89 23:12:14 GMT
References: <2510@bingvaxu.cc.binghamton.edu>
Sender: news@ncar.ucar.edu
Reply-To: hull@hao.UCAR.EDU (Howard Hull)
Organization: High Altitude Observatory/NCAR, Boulder CO
Lines: 19

No apologies necessary on your part, but I didn't say that the workbench
discard problem was a bug.  I asked if it was a bug.  Everyone seemed to
think that it was a feature.  One person from CBM said that it had been
reported to him by others who did think it was a bug, however he handled
these implications advisedly by explaining that it was not a bug.  So there
was nothing to correct, really.  So I suppose you might say it was "soundly
explained" (which is just as I like it to be) rather than "soundly corrected."

However, concerning the problem you brought up, do you have any other
details?  As, for instance, what sort of files, to your notion, were in
directories that produced a Guru upon invocation of the Workbench Discard
Menu Item?  Was this for OFS or FFS?  Did the drawer in question contain
a mix of files with and without icons?  Did it contain executables?  Were
any of the executables running at the time they were deleted?  Were there
any other CLI locks on the drawer or on other drawers in the drawer being
discarded?  For that matter, did the drawer discarded contain other drawers?
Just wondering...
					Howard Hull
					hull@hao.ucar.edu