Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!petrus!sabre!zeta!epsilon!gamma!ulysses!mhuxr!mhuxt!houxm!ihnp4!ucbvax!info-ridge
From: bogstad@HOPKINS-EECS-BRAVO.ARPA ("William J. Bogstad")
Newsgroups: mod.computers.ridge
Subject: Re:  IP/TCP support for ROS
Message-ID: <8512122128.AA01366@ucbvax.berkeley.edu>
Date: Thu, 12-Dec-85 14:10:27 EST
Article-I.D.: ucbvax.8512122128.AA01366
Posted: Thu Dec 12 14:10:27 1985
Date-Received: Fri, 13-Dec-85 09:09:41 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21
Approved: info-ridge@hopkins-eecs-bravo.arpa


	I am undoubtedly not the most qualified person to speak on this
subject, but in the interest of producing maximum confusion I will give
it a try.

	My understanding of ROS is that the "operating system" is
made up of several processes which handle various functions.  As an
example, there is a disk volume manager process, a file system manager
process, a tape driver process, etc.  The serial line IP/TCP code from
seismo is for the single kernel process used in 4.2BSD.  I suspect that
it would be possible to port this code to ROS, but it would require a
lot of work.  An additional problem results from the fact that ROS is
shipped as binary files without source code.  This would make it
impossible for a normal site to attempt the porting project.  I don't
know what Ridge policy is on giving outside organizations access to
source code so you would have to contact them directly.

	I hope this provides some information, at least why it isn't
likely to be down for awhile yet.

				Bill Bogstad