Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!sri-spam!ames!lll-lcc!lll-tis!ptsfa!hoptoad!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: Does RAM: ever retry?
Message-ID: <566@sugar.UUCP>
Date: Wed, 26-Aug-87 08:53:57 EDT
Article-I.D.: sugar.566
Posted: Wed Aug 26 08:53:57 1987
Date-Received: Sat, 29-Aug-87 09:21:22 EDT
References: <510@sugar.UUCP> <6619@eddie.MIT.EDU> <535@sugar.UUCP> <7069@steinmetz.steinmetz.UUCP>
Organization: Sugar Land UNIX - Houston, TX
Lines: 14
Keywords: RAM: out of memory RETRY CANCEL AllocMem

I still think it's gross...

> The 1.2 Ramdisk has a 'ripcord' of 30K of ram.  If it finds it can't get
> enough memory, it releases it's 'ripcord' and puts up the disk full
> requestor.   It won't agree to be un-full until it can get a ripcord
> back.  This was to solve problems of copying too much to the ram disk
> and having the system crash.  Without the 30K, it's hard to let the user
> know the ramdisk is full and let the user correct the problem.

But does that 30K have to be contiguous? And what's wrong with just saving
enough for the requestor? Surely a system requestor can fit in less than 30K.
-- 
-- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter
--                  U   <--- not a copyrighted cartoon :->