Xref: utzoo comp.unix.large:237 comp.unix.admin:1258
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!rpi!bu.edu!att!cbnewsh!wcs
From: wcs@cbnewsh.att.com (Bill Stewart 908-949-0705 erebus.att.com!wcs)
Newsgroups: comp.unix.large,comp.unix.admin
Subject: Re: Interesting Questions
Message-ID: <1991Mar17.045714.2709@cbnewsh.att.com>
Date: 17 Mar 91 04:57:14 GMT
References: <1991Mar12.005158.20343@erg.sri.com> <6Q.9Z1A@xds13.ferranti.com>
Organization: Here, beside the rising tide
Lines: 27

In article <6Q.9Z1A@xds13.ferranti.com> peter@ficc.ferranti.com (Peter da Silva) writes:
]In article <1991Mar12.005158.20343@erg.sri.com> zwicky@erg.sri.com (Elizabeth Zwicky) writes:
]> *i) What would a vendor install script that you didn't hate look like? 
]
]What the System V.3.2 install scripts look like. In fact the V.3.2 system
]administration/kernel configuration stuff is pretty damn good. Good enough

My main frustration with the System V Release N install scripts is
that they're all very picky about what order you install them in,
and that they're not documented in a way that lets me repackage them
(e.g. 3.5" -> 5.25" -> tape -> Ethernet).  The common USENET archiving,
which I think is named makekits and probably comes from Larry Wall,
is very nice about saying "This is part 03 of 15.  Please install 13 and 14."
You can take the kits, whether on floppy or email, and load them in
any order,  and if you have some kind of problem you don't have to
start over from scratch.

On the other hand, there was DEC's upgrade to SVR2.0 which had a bunch of
	cp /usr/src/uts/vax/cf/foo.c /usr/src/uts/vax/cf/foo.c.orig
	cp /new/foo.c /usr/src/uts/vax/cf/foo.c 
Better hope you've read the install script before using it, or else
hope it works perfectly the first time.....  which it didn't.
-- 
				Pray for peace;
					Bill
# Bill Stewart 908-949-0705 erebus.att.com!wcs AT&T Bell Labs 4M-312 Holmdel NJ
# Hacker.  System Designer.  Troublemaker.