SUMMARY:setld -i verses dupatch output

From: Gary Beckett <gbeckett_at_myra.com>
Date: Mon, 15 Oct 2001 14:10:25 -0700

Thanks to everyone that replied to my question. Seems that this is not
the easyest thing to determine.
One thing that I did learn was the syntax of the Patch subset name.
Thanks James S.
Take for example the following output from the "setld -i" command:
OSFPAT00034200440 installed Patch: Security (SSRT0617U)
(Security Related Patches)

000342 = the patch number
00 = the revision of the patch
440 = the OS version. In this case it is TRU64 4.0f

The output from the dupatch:
Patch 00465.00 - Security (SSRT0617U)

00465 = the patch number - minus the first "0"
00 = the revision of the patch

I would think that knowing these rules that it would be easy to
determine which patches needed updated by looking at the patch revision
number.
Not the case though. The revision number never changes from the "00"
suffix, and to make it worse, the patch number (in this case 000342) is
changed to 000465 in the lastest Pacth Kit DUV40FAS0006-20010620.
The "not so funny" thing is that I have the OSFPAT00034200440 security
patch installed, but when I run the Pre-Check installation for
DUV40FAS0006-20010620 it fails the check for the latest patch
OSFPAT000465.00 - Security (SSRT0617U).

Question: is the patch OSFPAT000465.00 - Security (SSRT0617U) not the
updated patch release for OSFPAT00034200440 - Security (SSRT0617U)

If I'm in error on any of this, please let me know, as I would like to
better understand the process of patch identification.


--
Gary Beckett
Myra Systems Corp.
gbeckett_at_myra.com
Received on Mon Oct 15 2001 - 21:11:29 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT