Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!think.com!linus!nixbur!nixpbe!peun33!mboen From: mboen@peun33.sni.de (Martin Boening) Newsgroups: comp.os.minix Subject: Re: Amiga & Atari minix 1.5 questions Message-ID: Date: 23 Jan 91 07:09:54 GMT References: <04036@avignon.gbdt.oz> Sender: news@nixpbe.sni.de Lines: 37 In <04036@avignon.gbdt.oz> Dave@avignon.gbdt.oz (Dave Moore) writes: >Just a brief question, > On the 68000 minix(s), are you limited to 64k code 64k data? > (I guessed you might be, as this is the easiest way to try and > stop a task from trashing another task) Well, it's been my experience that you aren't! (GCC is an example) Programs can have a large code segment and allocate lots of memory. However, many system calls use 'int' arguments (read, malloc, etc. come to mind), so the maximum for a single call to malloc has in my experience been 32 KB. (With unsigned it it might have been 64KB, but we don't use unsigned int). The same with read - you can't read more than 64KB in one read. (Or was that 32KB as well I'll have to check). So if you need large memory segments you'll have to go through a loop. Maybe someday somebody will come up with a 32-bit kernel for minix st. > Can the Amiga minix read Atari minix disks? That I don't know. The Atari MINIX file systems reside on standard format disks, so far as sectoring etc. is concerned. The fs code is supposed to be identical between MINIX PC and ST, so why not AMIGAMINIX as well. Therefore I'd think if you AMiga can read disks formatted by TOS (i.e. read the physical sectors from the tracks) there should be no problems. But I haven't tried it, so don't bet on it. > Dave. So long. Maybe some minix guru can verify/contradict what I've said? Martin -- Email: in the USA -> mboening.pad@nixdorf.com outside USA -> mboening.pad@sni.de Paper Mail: Martin Boening, Nixdorf Computer AG, SNI STO SI 355, Pontanusstr. 55, 4790 Paderborn, W.-Germany (Phone: +49 5251 146155)