Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!SCDPYR.UCAR.EDU!era
From: era@SCDPYR.UCAR.EDU (Ed Arnold)
Newsgroups: comp.sys.pyramid
Subject: Re: Pyramid Service
Message-ID: <8711182340.AA01492@scdpyr.UCAR.EDU>
Date: Wed, 18-Nov-87 18:40:04 EST
Article-I.D.: scdpyr.8711182340.AA01492
Posted: Wed Nov 18 18:40:04 1987
Date-Received: Sat, 21-Nov-87 12:51:58 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 18

I'd like to second Dave Bloom's earlier comments about Pyramid's
service.  Our techs feel they were badly burned by DEC service,
and I have, on a couple occasions, been less than impressed with Sun.
Our experience seems to indicate that Pyramid is, on the average,
certainly not worse than DEC or Sun.

On the issue of software upgrade, one thing that Pyramid did which
Sun never has done (my suggestion to Sun to get with the program on
this, fell on deaf ears), was to put together their rls/rlscmp utilities
that aid in locating site-specific customization.  The Sun manuals
blithely suggest that the system administrator make up a list of all
files than have been added or changed, before starting an upgrade, but
Sun provides no tools to do this.  Since Pyramid provides stock system
descriptions and tools that help one find mods & adds quickly, a busy
sys admin (who can't possibly remember, or even keep a record of, all
changes) doesn't have to put up with users calling for months afterward
with problems related to file changes that didn't get carried forward
after upgrade.