Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix
Subject: Re: RE: Ultrix problem
Message-ID: <1733@umcp-cs.UUCP>
Date: Tue, 1-Oct-85 22:03:40 EDT
Article-I.D.: umcp-cs.1733
Posted: Tue Oct  1 22:03:40 1985
Date-Received: Wed, 9-Oct-85 06:30:32 EDT
References: <1818@brl-tgr.ARPA>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 14

> ....  In both VMS and UNIX the kernel is loaded into low PHYSICAL
> memory while user processes tend to run in higher PHYSICAL pages.

I admit that I am no expert on VMS, but I believe that this is not
true: the VMS kernel is booted into the highest available physical
addresses.  (Physical location matters little once memory mapping
has been enabled.)  Were this not so, the problem might well have
struck VMS also:  The fault was traced to a RAM problem that was
masked by frequent writes, and it seems unlikely that VMS would
write on its code space.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu