Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!sequent!muncher.sequent.com!news
From: vandys@sequent.com (Andrew Valencia)
Newsgroups: comp.sys.hp
Subject: Re: HP-UX 8.0: memory mapped files?
Keywords: HP-UX mmap
Message-ID: <1991May4.045735.28909@sequent.com>
Date: 4 May 91 04:57:35 GMT
References: <1991Apr25.092827@ead.dsa.com> <64019@bbn.BBN.COM>
Sender: news@sequent.com (News on Muncher)
Organization: Sequent Computer Systems, Inc.
Lines: 25

fkittred@bbn.com (Fletcher Kittredge) writes:

>	The current version of HP-UX 8.0 dosn't seem to support memory
>mapped files; there is no mmap syscall.

Oh, hell.  I can't resist.

I ported the HP-UX 8.0 VM system to the 300 series before I left HP.
While I don't know if they've really sealed it off for release, I can tell
you that exec(), shared libraries, etc. are all based on top of true
memory mapped files.  In fact, if I'm reading into Mr. Sabatella's paper
(on shared libraries) correctly, a user-level interface must exist.

From the release literature, I take it that they certainly are not
documenting/supporting memory mapped files yet.  But how are OS
maintainers going to get their grey hair if you guys don't go out and
monkey with the unsupported interfaces? :-)

If somebody goes for it, please post and tell us if they found whether
read/write is coherent with the mmap'ed region or not.  I'd just love
to know how far they got.

				I'll go back to my hole now...
				Andy Valencia
				vandys@sequent.com