My original question:
>
> Managers,
>
> I am going to upgrade soon to v4.0 from v3.2D-1 on an Alpha 1000 4/233
> and I have heard that you need to deinstall all patches before upgrading.
> How do I know what patches are already installed? Is there a way to tell?
>
Thanks to:
John Schaeffer jsch_at_conncoll.edu
Kurt Carlson sxkac_at_java.sois.alaska.edu
Response:
The responses I got, were that when you install patches, you should put a
copy of the readme in /etc/patches so that you can keep track of what patches
you have installed on your machine.
Concerning an upgrade, Kurt wrote this:
>We've not yet had to write the de-install script to back a patch off,
>it would be very easy to do with the method we install.
>However, this does you no good for your present situation.
>You should not need deinstall patches with the upgrade (with a few possible
>exceptions, generally only for customized patches which may not be sync'd
>for a particular version and for patches to include or source modules),
>particularly with an installupdate upgrade vs. a setld upgrade... i believe
>installupdate tends to rebuild everything. Going v3.2d-1 to v3.2g (setld)
>we had to remove only 1 of 44 patches, we knew that was likely because
>it was a custom patch and has to be sync'd closely with the advfs
>consolidated patch. With the setld upgrade the process is to check what
>got rolled into the new version (most did) and simply review compatability
>of those which weren't rolled in.
Thanks everyone.
------------------------------------------------------------------------------
Karen Thomas
Connecticut State University System Office
Information System
THOMASK_at_CTSTATEU.EDU
PHONE: (860) 493-0118
Received on Wed Nov 06 1996 - 17:08:02 NZDT