🚀 go-pugleaf

>>>    have a lot more respect for Sun's version of Unix than Unisoft
 
>>of, say, System V.  You'd also loose (a) streams, (b) the toolbox, (c)
>>more solid networking code (although Sun 3.4 looks better than their
>>previous efforts), ...
 

You're a funny guy if you think that Unisoft's networking code is more 'solid'
than Sun's code. I know of many OEMs who have not been thrilled with Unisoft's
code.  I say the Mac toolbox access from AUX will not pan out like everybody
seems to think it will. Access to the toolbox is single threaded. Why would 
anyone want a single threaded graphics environment on top of a multitasking 
kernel? Why not just use X or NeWS if you are running A/UX? Have you seen the
number of toolbox managers that don't work (yet) under A/UX? 

A Sys V File System on top of a I/O subsystem like in the Mac II will be SLOW.
Unisoft uses *Sun's* Virtual File System design to support NFS but retains the
standard Sys V file system.

At least Unisoft put in some BSD features (sockets, select) and some of *Sun's*
efforts (NFS, Virtual File System). But A/UX is not BSD. Period.

-- 
John LaLonde
Systems Engineering Group
Nicolet Instrument Corporation
uucp: {ihnp4,seismo,decvax,harvard}!uwvax!nicmad!lalonde