From owner-mint@fishpool.com Tue Sep 16 10:47:12 2003 Date: Tue, 16 Sep 2003 10:43:48 +0200 To: "[MiNT] Mailing-List" Subject: Re: [MiNT] Correct way to detect memory protection Message-ID: <20030916084348.GA32463@hrzpub.tu-darmstadt.de> Mail-Followup-To: gryf, "[MiNT] Mailing-List" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i From: Thomas Binder X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-5, required 5, EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, REPLY_WITH_QUOTES, USER_AGENT_MUTT) 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: gryf@hrz.tu-darmstadt.de Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: Hi! On Mon, Sep 15, 2003 at 11:33:10PM -0400, Lonny Pursell wrote: > [...] If Sysconf(-1) returns anything != -32L, you can safely > use memory protection flags in calls to Mxalloc(). [...] > > Thus, Sysconf() shouldn't be used to detect the presence of > MiNT, but to decide whether to use memory protection flags with > Mxalloc(). > ====================================================================== > > My question is: > I just did a test on magicmacX and sysconf(-1) returned a "2". > So has magic started to support proper memory protection or have > I made a mistake in my test? Well, of course MagiC dose not support memory protection. But if you read the mail you quoted carefully, you should find the answer yourself: There's a difference between being able to pass memory protection flags to Mxalloc() and memory protection being active ... The problem the old mail was referring to is that some versions of TOS (3.something) support Mxalloc(), but behave strangely (up to and including crashes) when you use memory protection flags. _No_ statement was made about the actual availabilty or activity of memory protection. Ciao Thomas -- Thomas Binder (Gryf @ IRCNet) gryf@hrzpub.tu-darmstadt.de PGP-key available on request!