Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!agate!web-3d!c60c-3gf
From: c60c-3gf@web-3d.berkeley.edu (Philip Brown)
Newsgroups: comp.os.os9
Subject: Re: Reposting : Need info about OS-9 !!
Message-ID: <1990Nov7.035523.9612@agate.berkeley.edu>
Date: 7 Nov 90 03:55:23 GMT
References: <4492@iitmax.IIT.EDU>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Distribution: usa
Organization: University of California, Berkeley
Lines: 28

In article <4492@iitmax.IIT.EDU> demorks@iitmax.iit.edu (Raja K. Sarma) writes:
>Hi,
>   Could someone shed more info on OS-9 or direct me to a good book.      
>I am looking in particular about scheduling and interprocess communication
>implementation in OS-9 (or probably any extensions of OS9.*), also I would
>appriciate if I could get info on how different it is from other systems.

As far as I know, its closest relative is UNIX.  I am only familiar with
OS9 "level II", implemented only on the Color Computer 3, as far as I know.
At any rate, when it comes to inter-process communication (presumably you
mean concurrently running processses, one has the choice of
1) signals (limited to a byte, or a word, depending on your system)
2) ram-disks or pipes
3) "get/put" buffers.
1 & 2 should be self-explanitory.

(3) is done by defining special buffers that are system-wide.  Any process
can read them.  They are mapped into the process address space by a system
call.  When a process changes its mapped buffer, that change is echoed
system-wide.

That all the options I know of, though I hear that the full version has
proper UNIX TCP/IP protocols (interprocess communication, through "sockets")

-----------------------------------------------
If you desire an Email argument, Reply to:
Pbrown@ocf.berkeley.edu
  Moral:  ALWAYS read the signature!