Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!ernie.Berkeley.EDU!carlson
From: carlson@ernie.Berkeley.EDU (Richard L. Carlson)
Newsgroups: comp.sys.amiga.tech
Subject: Re: divide by 0 problem in "info"?  Also: GOMF
Message-ID: <25918@ucbvax.BERKELEY.EDU>
Date: 3 Sep 88 04:39:07 GMT
References: <8808311804.AA19391@cory.Berkeley.EDU> <4645@cbmvax.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: carlson@ernie.Berkeley.EDU.UUCP (Richard L. Carlson)
Organization: University of California, Berkeley
Lines: 26

In article <4645@cbmvax.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes:
<In article <8808311804.AA19391@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
<<
<<:Honest!  It really happened to me.  I just innocently typed "info" at my
<<:CLI.  It gave me a list of mounted disks and their used space, free,
<<
<<	This is a bug in RAM: ... sometimes it looses track of the number
<<blocks free / allocated and it becomes 0.  INFO assumes that disk devices
<
<Actually, there was a bug in the info command, and a bug in ram.
<Info assumed 2 reserved blocks, rather than reading the environment
<vector.  (It also didn't check for a possible divide by 0).  I fixed
<both for 1.3.  RAM also had a bug, involving deleting directories.
<(essentually, the block count became 1 off)  I fixed than one, too.
<-- 
<andy finkel		{uunet|rutgers|amiga}!cbmvax!andy

The bug in RAM: involved just deleting directories?  I've recently been
doing some heavy-duty *file* creation and deletion in RAM:, and I always
end up with very negative block counts for RAM: [-118 blocks, as I type
this].  Are there circumstances other than deleting directories that are
known to induce this bug?

-- Richard
   {tektronix,dual,sun,ihnp4,decvax}!ucbvax!ernie!carlson
   carlson@ernie.berkeley.edu