BSD 4_2 development
[unix-history] / usr / doc / hints / 03.t
CommitLineData
0a99cd43
C
1.sh OVERVIEW
2We first discuss components, listing the alternatives we have tried
3and sometimes a few we have not, and then discuss system packages.
4We buy a substantial portion of our equipment from vendors other
5than DEC.
6The reasons
7for choosing second vendor equipment are usually
8some combination of more current technology, lower cost for
9equivalent equipment or shorter delivery time.
10.LP
11We do not consider devices that have
12proven unreliable or whose performance
13we consider inadequate.* In addition,
14.FS
15* An exception to this rule is made where we have yet to
16find any satisfactory devices in a particular category.
17In these instances we have
18indicated our reservations about the existing choices
19in the hopes that new products will address the problems
20we believe are important. The reader should realize that
21if a vendor's equipment has been mentioned in a negative
22light it indicates we at least thought highly enough of it
23to evaluate it
24seriously. We are not trying to damage any company's reputation,
25merely insure that important information is shared equally.
26.FE
27there are many devices that we
28have no experience with.
29As a general rule, every new peripheral has required
30a non-trivial amount of leg work to get up to speed.
31We suggest using
32only peripherals that have been previously used successfully on
33.I
34the type of VAX you are configuring
35.R
36(780, 750 or 730)
37or
38demanding a substantial (50-100%) discount for being
39a guinea pig.
40Be especially careful of UNIBUS\(dg interfaces.
41Almost every manufacturer of a UNIBUS widget now includes the VAX
42as a machine on which his device will work.
43Some of these devices have still not been well tested in this situation.
44These often will not work without substantial modification.
45.LP
46.I
47System buyers without ready access to an in\-house hardware staff
48should consider carefully the option of buying as much DEC equipment
49as possible.
50.R
51If you have the money and time required to do this,
52there are some strong advantages.
53Our DEC equipment has, in general, proven somewhat more
54reliable than the equivalent alternate vendor equipment.
55Time from equipment delivery to running system is also usually shorter.
56DEC field service in our area is excellent.
57Outside service available for non-DEC peripherals is spotty at best.
58.LP
59For smaller installations this option should be carefully considered.
60It is easier if you can call one party for all your problems, if you can
61afford it.
62At Berkeley, we are well past the inventory level where self maintenance
63begins to pay off even on all DEC systems, so this is not a
64consideration.
65One of us (Kridle) manages our local hardware support group.
66.LP
67Unfortunately, the limited selection of configurations currently available
68sometimes make the all-DEC choice difficult.
69This is especially true of the smaller configurations as
70DEC's bottom end peripherals are less satisfactory for UNIX.
71We say this not just for monetary reasons; functionally and aesthetically
72we would prefer to have neither the RK07 disk
73nor the TS11 tape unit in any system we have to deal with.
74.LP
75We recommend getting field service at least on your CPU
76for the first year.
77It has paid off for us in the cost of parts alone.
78You can drop the contract after the engineering changes have
79tapered off and most of the infant failures have occurred.
80DEC requires a certain amount of its peripheral equipment on the machine to
81qualify
82for field service.
83We understand that it is company policy not to
84provide a maintenance contract for a system
85without a DEC mass storage peripheral.
86If you intend to purchase a maintenance contract, be certain
87that your local field service is willing to support at least the DEC
88equipment you buy.