Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!saturn!jps@wucs1.wustl.edu
From: jps@wucs1.wustl.edu (James Sterbenz)
Newsgroups: comp.os.research
Subject: Re: Question for the week -- distributed Multics?
Message-ID: <6327@saturn.ucsc.edu>
Date: 10 Feb 89 20:43:12 GMT
Sender: usenet@saturn.ucsc.edu
Organization: Washington University, St. Louis, MO
Lines: 32
Approved: comp-os-research@jupiter.ucsc.edu


In article 6238 raspail!bga@shamash.cdc.com (Bruce Albrecht) writes:

>CDC's NOS/VE is a Multics derivative...

I'm somewhat familiar with NOS/VE, and am very glad that with the demise of
Honeywell supported Multics, the important ideas live on in a commercial
product (there are other Multics derivatives, but NOS/VE seems to be the
closest).  

>CDC's NOS/VE has a file server, which is a process that communicates with 
>the file servers on the other machines.  When a shared segment is accessed, 
>the file server sends requests for reads to the machine on which the segment 
>actually resides (i.e., the machine to which the disk is connected.)

I'd be interested in more information on this.  I know nothing about CDC
networking.  My research involves virtual memory management across the
network.  I use a Multics-like base, but am also very concerned with the
host hardware architecture and transport protocol design, which are 
optimised to work efficiently with the memory management.  How does CDC
integrate NOS/VE memory management with network hardware and protocols?

Is there anything published on this?  (The CDC manuals I have do not 
discuss the remote file access or any aspect of communications).
Is a CDC NOS/VE or Cyber 800 communications type person on the net that
could enlighten me?

-- 
James Sterbenz  Computer and Communications Research Center
                Washington University in St. Louis 314-726-4203
INTERNET:       jps@wucs1.wustl.edu
UUCP:           wucs1!jps@uunet.uu.net