Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!boulder!sunybcs!ugkamins From: ugkamins@sunybcs.uucp (John Kaminski) Newsgroups: comp.sys.amiga.tech Subject: Re: Unix V7 functionality under (or along with) AmigaDOS? (*LONG*) Message-ID: <5171@cs.Buffalo.EDU> Date: 11 Apr 89 03:51:13 GMT References: <6406@cbmvax.UUCP> <6464@cbmvax.UUCP> <3689@sugar.hackercorp.com> <14465@gryphon.COM> Sender: nobody@cs.Buffalo.EDU Reply-To: ugkamins@sunybcs.UUCP (John Kaminski) Organization: SUNY/Buffalo Computer Science Lines: 17 In article <14465@gryphon.COM> keithd@gryphon.COM (Keith Doyle) writes: >BTW, what does the UNIX call look like to allocate CHIP ram vs FAST ram? :-> > >Keith Doyle >keithd@gryphon.COM gryphon!keithd gryphon!keithd@elroy.jpl.nasa.gov hee hee....That actually has a serious note. The UNIX standard for malloc() has no defined semantic for types of memory, at least that I'm aware of. How about a real far out concept which has been talked about extensively on comp.os.minix and I don't know much about: what are the semantics of POSIX, in this case, malloc() ? Does *IT* deal with the possiblity of differing memory types? Well, I would hope for portability's sake, you wouldn't be that hardware- specific, and let the OS handle such hardware dependancies. That's what having an OS is all about in the first place!! hmmmmm.....graphics rendering with a bunch of ioctl()'s and write()'s ......hmmmmmmmmm!!!!!!