🚀 go-pugleaf

In article <1990Dec31.151103.2735@cbnewsl.att.com>, ramesh@cbnewsl.att.com (nallepilli.s.ramesh) writes:
> [ A commentary on some reinstallations vs. upgrades. ]
> 
> Is there a way to install the new subsets without thrashing user modified
> setup files?

	It depends on the versions.  Hopefully the following will
	be a list of the variations:

		V3.0 to V3.1 - This was distributed as a real upgrade.

		V3.x to V4.0 - This is a full reinstallation.  Nothing
		to do, but remember all the files you've changed and
		restore them.

		V3.x to V4.1 - Reinstallation.

		V4.0 to V4.1 - At the moment V4.1 is a complete installation.
		Sometime soon, the V4.1 upgrade will be available.

	The way an upgrade is done is to delete everything in the
	old subset, then install the new subset.  In some cases we
	just overwrite the old pieces of the subset.  The problem
	with deleting all the old stuff is that when the BASE subset
	goes, many of the programs needed by the upgrade also go and
	the upgrade falls over on it's face.

> On a similar note I have a non DEC disk that is used for /usr . Unfortunately
> I am unable to specify it in the installation procedure, since the
> system doesn't recognise it. (It is a wren VI)  This means I have to first
> load the SW to a DEC disk and then copy the whole /usr tree to the WRENVI.
> 
> Is there a way out??

	None that I know of, though you might try looking at the
	scripts left around by the installation procedure to see
	you they can be hacked.  Such hacking is of course UNSUPPORTED
	and if you have any problems because of it, you're on your
	own.
> 
> N. Ramesh (att!harpo!ramesh)
-- 
Alan Rollow				alan@nabeth.enet.dec.com