Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!uflorida!ziggy!screamer!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.unix.sysv386 Subject: SCO Unix: few bugs but bad features Message-ID: <26EFE2A9.CC4@tct.uucp> Date: 13 Sep 90 19:48:57 GMT References: <33718@cup.portal.com> Organization: Teltronics/TCT, Sarasota, FL Lines: 18 According to oscar@eismond.uucp (Carsten Tschach): >Not SCO - it's so buggy !!! I have found SCO's products to be relatively less buggy than most other vendors' products. We use SCO Unix 3.2v0, and we have found it of good quality. Most of the bugs we found are fixed in 3.2v2. However, I often disagree with the set of features SCO chooses to implement. The SCO Unix C2 security, for example, has driven us *this* close to changing vendors. C2 security is a nightmare for support. Imagine trying to debug permission problems when both system programs and the *kernel* care *which* user and group you are, and grant different permissions for each. Ah for the good old days, when the only choices were "superuser" and "peon"... -- Chip Salzenberg at Teltronics/TCT ,