Path: utzoo!attcan!utgpu!watmath!iuvax!mailrus!ulowell!swan!arosen From: arosen@hen.ulowell.edu (MFHorn) Newsgroups: comp.unix.ultrix Subject: Re: ultrix 3.1 Message-ID: Date: 2 Aug 89 16:10:25 GMT References: <7463@cbmvax.UUCP> <288@edison.UUCP> <1410@riscy.dec.com> <579@mmlai.UUCP> <7505@cbmvax.UUCP> Sender: news@swan.ulowell.edu Organization: University of Lowell, CS Dept Lines: 27 In-reply-to: grr@cbmvax.UUCP's message of 2 Aug 89 09:42:29 GMT In article <7505@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes: In article <579@mmlai.UUCP> burzio@mmlai.UUCP (Anthony Burzio) writes: > A user should not have to do these operations manually. Ideally, it > IS possible to have a program that lets you pop in a tape, press > install all, and wait for the COMPUTER to do all the rest... Sure, but requiring it to be so simple and devoid of intelligent intent sort of presupposes you needn't have anybody handy capable of picking up the pieces if something goes wrong, interpreting change notes, and preserving local color? You might like something more like DG's installation procedures. It checks with the operator before any major step and does error checking on everything it does. If something goes wrong, it tells you about it, tells you where it put the errors and asks what you want to do. It'll also tell you if you have to do anything manually for changes to take effect. It does this thoroughly and consistently throughout all the administrative scripts it has, which cover ttys, printers, tapes, disks, files, kernels, users, uucp, tcp/ip, layered software, etc. -- Andy Rosen | arosen@swan.ulowell.edu | "I got this guitar and I ULowell, Box #3031 | ulowell!arosen | learned how to make it Lowell, Ma 01854 | | talk" -Thunder Road RD in '88 - The way it should've been