Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: ultrix 3.1
Message-ID: <7505@cbmvax.UUCP>
Date: 2 Aug 89 09:42:29 GMT
References: <7463@cbmvax.UUCP> <288@edison.UUCP> <1410@riscy.dec.com> <579@mmlai.UUCP>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 27

In article <579@mmlai.UUCP> burzio@mmlai.UUCP (Anthony Burzio) writes:
> In article <1410@riscy.dec.com>, graham@fuel.dec.com (kris graham) writes:
> > UWS is also very simple.
> > - Move the new kernel to root (after saving the old one).
> > - /etc/reboot
> 
> 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?

I've complained before that Ultrix installation procedures are getting
too user friendly of at least fail to provide an alternate track and
documentation to enable an experienced administrator to his job in an
efficient manner.  Maybe this is only a reflection of some underlying
need for job security...except I'm playing electrical engineer these
days on only doing Unix administration to make sure the system serves
me!

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)