From owner-mint@fishpool.com Tue Aug 19 12:36:38 2003 Date: Tue, 19 Aug 2003 12:23:15 +0200 From: Adam Klobukowski To: mint@fishpool.com Subject: Re: [MiNT] Alt Ram Troubles - 2 Message-Id: <20030819122315.3b60b8a3.atari@gabo.pl> In-Reply-To: References: <1060829593.19355.1.camel@pikachu.atari-source.com> <20030819103432.A24927@pc272.hrzpub.tu-darmstadt.de> X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: atari@gabo.pl Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: On Tue, 19 Aug 2003 11:27:09 +0200 (CEST) Frank Naumann wrote: > Hello! > > > > The maxmem parameter was set around 4096Kbytes. I wouldn't > > > think that this parameter would exhibit the effect > > > > Well, it does, and the reason's quite simple: If you limit the > > memory available for programs via MAXMEM, Malloc(-1) will of > > course report only that amount of memory the process is allowed to > > allocate, not what is actually free in the system. > > As a side note, MAXMEM is obsoleted. Thomas introduced the much better > INITIALMEM setting that limit the size of the stacksegment on Pexec() > (it default to 4MB). Why not remove it from 1.16a? (and add a warning note if it is present in mint.cnf) -- Semper Fidelis Adam Klobukowski atari@gabo.pl