Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!emory!utkcs2!stc06!abg
From: abg@stc06.ornl.gov (BANGS A L)
Newsgroups: comp.realtime
Subject: Re: Survey of Commercial Real-Time Operating Systems II
Message-ID: <1990Aug16.211418.3293@cs.utk.edu>
Date: 16 Aug 90 21:14:18 GMT
References: <3036@zipeecs.umich.edu> <1990Aug13.123602.509@uunet!unhd> <6651@tekcrl.LABS.TEK.COM>
Sender: news@cs.utk.edu (USENET News System)
Reply-To: abg@stc06.ctd.ornl.gov (BANGS A L)
Organization: Oak Ridge National Lab
Lines: 23

In article <6651@tekcrl.LABS.TEK.COM> rjn@snowbird.LABS.TEK.COM (Jim Nusbaum) writes:
>In article <1990Aug13.123602.509@uunet!unhd> rg@unhd.UUCP (Roger Gonzalez ) writes:
>>
>>>8. pSOS
>>>
>>>   - UNIX-compatible kernel, < 12K
>>      ^^^^^^^^^^^^^^^^^^^^^^
>>No it isn't.  Not even remotely.  It's small, fast, but crippled.  We've
>>spent more time trying to *make* it Unix compatible than I care to think
>>about.  We're moving to VxWorks, with luck.
>>
Ok, time for my two-bits.  I have been looking very closely at VMEexec,
which gives you the power of the pSOS+ kernel with some nice stuff
added by Motorola, including SVIDlib, a Unix library, and communications
to make ethernet and backplace communications transparent.

It seems that SVIDlib would make pSOS a tolerable product for those of
us who are looking to do Unix development but want to run the final
product in real-time.

Alex
Alex L. Bangs ---> bangsal@ornl.gov         Of course, my opinions are
Oak Ridge National Laboratory/CESAR            my own darned business...