Path: utzoo!utgpu!watmath!clyde!att!rutgers!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!lll-winken!arisia!quintus!sri-unix!orawest!brian
Newsgroups: comp.unix.questions
Subject: Xenix compatibility
Summary: How Un*x is it?
Keywords: xenix compatibility
Message-ID: <325@orawest.UUCP>
Date: 7 Dec 88 18:12:59 GMT
Reply-To: orawest!brian@unix.sri.com
Followup-To: orawest!brian@unix.sri.com
Distribution: na
Organization: Odyssey Research Associates, West; Menlo Park, CA
Lines: 32
Return-Path: 
To: sri-news@mailhost





Call for opinions:

We are beginning development of an 8 staff-year Unix application.
This application is semi-distributed, using TCP/IP for communications
between servers running on different machines connected by ethernet.
Our current system is a Sun network, but due to some peculiar
requirements (aka US gov't :-) we are looking at AT&T Sys V.4 and
Microsoft Xenix 2.0, the latter alleged to be equivalent to Santa Cruz
Operations (SCO) Xenix 2.2.  I would appreciate reasoned or impassioned
responses concerning Xenix; in particular:

	Is Microsoft Xenix 2.0 actually the same as SCO Xenix 2.2?

	How does Microsoft Xenix 2.0 differ from current SCO offerings?

	How compatible is Xenix with AT&T V.3, and by extension V.4?

	What is the development environment like for Xenix?

	Is Xenix brain-dead in any/many significant areas?

	What network support exists in Xenix (NFS, XDR, rsh, etc.)?

	What performance can I expect from an AT clone with a 20MHz 386,
	4M of memory, and a 28ms 40MB hard disk running a 80286 version
	of Xenix?  Compared with a Sun 3/50 or 3/60 with 4M and SCSI?

Thanks.


-- 
B<   Brian Kahn, Odyssey Research West   orawest!brian@unix.sri.com