Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: AT&T "nth Edition" vs. "Release n"
Message-ID: <10596@dog.ee.lbl.gov>
Date: 5 Mar 91 01:16:35 GMT
References: <6798@idunno.Princeton.EDU> <1991Mar3.233814.14234@frey.newcastle.edu.au> <10556@dog.ee.lbl.gov> <15385@smoke.brl.mil>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 19
X-Local-Date: Mon, 4 Mar 91 17:16:35 PST

In article <15385@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
>In fact UNIX System V was not using the virtual memory system to which
>Chris refers any time in the recent past.  Before the switch to VM a
>la Sun, UNIX System V had been using a "region"-oriented system based
>on concepts similar to DEC's VAX/VMS.

Not on the 3B2. :-)

(The problem with talking about `System V' is that the four `Release N's
are completely different, and a `Release N' for machine A is completely
different from a `Release N' for machine B.  The region VM was in the
VAX versions of VR2 and VR3, and maybe even VR1, if my faulty memory is
giving the right answers.  But the System V source trees for different
platforms were entirely separate.  Keith Bostic once had an argument with
some USDL-type who claimed that merged trees were impossible, even
though 4.3BSD-tahoe had already shipped!)
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab EE div (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov