Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!jpd00964
From: jpd00964@uxa.cso.uiuc.edu
Newsgroups: comp.sys.next
Subject: Re: Pager Objects
Message-ID: <246300075@uxa.cso.uiuc.edu>
Date: 19 Dec 89 10:35:30 GMT
References: <5999@ubc-cs.UUCP>
Lines: 21
Nf-ID: #R:ubc-cs.UUCP:5999:uxa.cso.uiuc.edu:246300075:000:896
Nf-From: uxa.cso.uiuc.edu!jpd00964    Dec 18 22:54:00 1989


/* Written  1:13 pm  Dec 17, 1989 by morrison@cs.ubc.ca in uxa.cso.uiuc.edu:comp.sys.next */
/* ---------- "Pager Objects" ---------- */
>I have been pouring over the Mach documentation provided with the
>NeXT. It is vaguely suggested (Ch 16 of the NeXT Ref Man) that an
>alternate pager object may be associated with a task. Further reading
>tends to falsify this suggestion, and there doesn't appear to be any
>evidence (e.g. in proc.h) that this is supported in the version of Mach
>running on the NeXT.
>
>Do other implementations of Mach allow alternate
>pagers or have I just encountered forward references to features
>not yet supported?

Carneghi Mellon (however it is spelled) has their mach manual in a downloadable
form through anonymous ftp.  I forget the address, but somone should know it.

I really recommend going through that rather than the NeXT manual.

Michael Rutman
SoftMed