Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!nysernic!itsgw!batcomputer!cornell!uw-beaver!mit-eddie!ll-xn!ames!sdcsvax!ucbvax!PEANUTS.NOSC.MIL!dennis
From: dennis@PEANUTS.NOSC.MIL.UUCP
Newsgroups: comp.sys.apollo
Subject: Re: Updating Large Rings
Message-ID: <8709300011.AA14044@cod.nosc.mil>
Date: Tue, 29-Sep-87 20:18:31 EDT
Article-I.D.: cod.8709300011.AA14044
Posted: Tue Sep 29 20:18:31 1987
Date-Received: Fri, 2-Oct-87 06:37:15 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 17

[referring to Dave Krowitz's binary installation scheme...]

Clever, Dave.  But how do you answer all those questions endlessly
asked by the installation programs--in a script made up ahead of time?
If so, then every installation needs a different script, right?  This
also assumes that every node gets the same software (which I've just
about decided is the only way to maintain sanity).

Still, it seems to me what you would like to have is a master network
configuration description.  Then an installation for Pascal, for
instance, would look at the network configuration to find which nodes
get it (and which only get links) and would go ahead and install it.
The installation program could use your binary installation scheme to
speed things up if the configuration allowed for it.

	Dennis Cottel  Naval Ocean Systems Center, San Diego, CA  92152
	(619) 225-2406      dennis@nosc.MIL      sdcsvax!noscvax!dennis