Newsgroups: comp.unix.sysv386
Path: utzoo!telly!eci386!jmm
From: jmm@eci386.uucp (John Macdonald)
Subject: Re: Compatibility lists
Message-ID: <1990Nov13.172607.12087@eci386.uucp>
Reply-To: jmm@eci386.UUCP (John Macdonald)
Organization: Elegant Communications Inc.
References: <1990Nov11.143254.2666@pegasus.com> <1990Nov12.050252.3159@usaos.uucp> <1990Nov12.070444.8046@ico.isc.com>
Date: Tue, 13 Nov 90 17:26:07 GMT

In article <1990Nov12.070444.8046@ico.isc.com> rcd@ico.isc.com (Dick Dunn) writes:
|Two cautions on these "compatibility lists":
|	- They get out of date in a big hurry.
|	- A software vendor's list includes what has been checked out in
|	  one way or another; thus while presence of some hardware on a
|	  list is a good sign, absence is not necessarily a bad sign.

In addition, you have to worry about the number of on-board switches,
installation options, and kernel options that are available.  Just
because one person succeeds or fails to amke a combination of
hardware and software work does not mean that someone else (or even
the same person working from a different starting point) will be
able to duplicate that success or failure.  Aren't open systems
with minimal standards fun?
-- 
Cure the common code...                      | John Macdonald
...Ban Basic      - Christine Linge          |   jmm@eci386