Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!stanford.edu!agate!violet.berkeley.edu!ilan343
From: ilan343@violet.berkeley.edu (Geraldo Veiga)
Newsgroups: comp.unix.sysv386
Subject: Re: wanted: UNIX or clone
Message-ID: <1991May1.185355.12728@agate.berkeley.edu>
Date: 1 May 91 18:53:55 GMT
References: <1991Apr28.225644.10469@nstar.rn.com> <1991Apr29.031654.17360@agate.berkeley.edu> <281ECF1C.1D46@telly.on.ca>
Sender: root@agate.berkeley.edu (Charlie Root)
Organization: University of California, Berkeley
Lines: 31

In article <281ECF1C.1D46@telly.on.ca> evan@telly.on.ca (Evan Leibovitch) writes:

> Rick Richardson posted (July 31, 1990) an article on the
>incompatabilities between the console ioctl values of the major 386 UNIX
>vendors. ESIX's values matched the AT&T release exactly, while both ISC
>and SCO strayed (in different ways).

Could anyone that saved a copy of this article repost it (or mail it to 
me)?

>The best way to check compatability, regardless of what platform you're
>buying from, is to go to a knowledgable vendor/dealer who has pre-tested
>what they're selling you. That was always important for hardware, it's
>also often important for software too.

Not if you are buying an inexpensive, high-volume product.  This should
be the case with general purpose word processors, spreadsheets etc.
I wish I could buy them from perfectly ignorant dealers.   This is
the case with hardware in the PC clone world.  Your favorite computer
clone-maker down the street sells machines that work with very minimal
support from their part.  Of course, multi-user systems and 
some specialized applications are a different story entirely, even
under DOS.

>That proponents of ISC and/or SCO would say that only their platforms will
>properly run 386 UNIX software is no more than marketing hype at best and
>scare tactics at worst. 

Well, they have numbers on their side.  It would be crazy for a 386
software developer not to support SCO, regardless of how much they
deviate from the standard UNIX 386.