Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!ames!lll-lcc!ncis.tis.llnl.gov!helios.ee.lbl.gov!pasteur!agate!saturn!munnari!murdu.oz.au!pal@uunet.UU.NET
From: munnari!murdu.oz.au!pal@uunet.UU.NET
Newsgroups: comp.os.research
Subject: Re: CDC NOS/VE
Message-ID: <6841@saturn.ucsc.edu>
Date: 7 Apr 89 04:29:49 GMT
Sender: usenet@saturn.ucsc.edu
Lines: 38
Approved: comp-os-research@jupiter.ucsc.edu


In article <6792@saturn.ucsc.edu> jps@wucs1.wustl.edu (James Sterbenz) writes:
>
>In article <6768@saturn.ucsc.edu> ken@gatech.edu (Ken Seefried iii) writes:
>>
>>Could someone point me to references concerning the design of CDCs
>>NOS/VE operating system.
[deleted]
>Most of what I know I've gotten from the hardware manuals; for some
>information, such as virtual memory management, they are useful.
>Try looking at:
>"CDC Cyber 170 and Cyber 180 Volume I: Virtual State System Description,
>Functional Description", 60462090, 1984,
>and
>"CDC Cyber 170 and Cyber 180 Volume II: Instruction Descriptions, Programming
>Information", 60458890, 1984.

Another manual that describes NOS/VE is:
CDC Cyber 170 and Cyber 180: General Description (Hardware Maintenance Manual)
no. 60459960, 1985.

The preface states that "this manual provides a model-independent overview of
the Virtual State System and its security/protection and interrupt features
relative to the computer system's hardware." Actually in the version I have
(revision B) the first section (virtual state overview) and the last
section (virtual state software overview) are omitted. Other
sections are called "security and protection", "buffer memories",
"central processor logical environment", "interrupts", 
"call/return/pop mechanism", "crossing protection boundaries", 
"interrupts part II", and "debug".

This manual, being an overview, also has the advantage that it's short in
length, unlike some other manuals such as the FORTRAN ones and the CDCNET
shelf :-)

Phil Leverton
Systems Group, University Computing Services,
University of Melbourne.