Summary: Tru64 version string did not change for 5.1B-3

I guess I was never aware the the version string didnt change
for patck kits.

Thanks to all who replied. Their answers and suggestions are below...

Bugs

My original quiestion:

On Wed, 8 Mar 2006, Bugs wrote:


I just installed patch 5 (5.1B-3), but uname shows the
same verion as I had before:
uname -va
OSF1 oak V5.1 2650 alpha

My previous version was 5.2B PK4.

I ran versw:
> versw -switch
Failure to switch versions because the new version is older than than the active
version

Patch tracking shows the 5.B-3 installed:

  Date     Time   Prd     Patch       Operation   KitName
  ----     ----   ___     _____       _________   _______
2006/03/08 12:40 DU  Patch   26115.00 Installed T64V51BB26AS0005-20050502
2006/03/08 12:40 DU  Patch   26114.00 Installed T64V51BB26AS0005-20050502
2006/03/08 12:40 DU  Patch   26113.00 Installed T64V51BB26AS0005-20050502
2006/03/08 12:40 DU  Patch   26110.00 Installed T64V51BB26AS0005-20050502


The patch install seemed to go smooth. I ran with single user mode with network.
I did the kernel build, replaced the kernel, and rebooted.

Any reason why the version string did not change?

File that I used = T64V51BB26AS0005-20050502.tar



>From Roberto.Mackun

V5.1B-3 is merely a product specification for a specific release. V5.1B-3 is
in fact exactly identical to V5.1B except it includes the New Hardware
Delivery 7 CD (I think its 7) and PatchKit 3.

The only way to confirm if you have this particular revision installed is:

# sizer -v
# dupatch -track -type kit

===============================================================

>From davegu1

Check the status of the patch log and see if any new events were logged in
the event log
/var/adm/patch/log/

===============================================================

From: Dr. Thomas P. Blinn

Uname doesn't change.  Never has.  Check sizer -v which should show that you
have the new kernel.  Can't say why versw wasn't happy; never really managed
to understand the rules it tries to apply to sort things out.

===============================================================

>From ems

Have you tried command

     /usr/sbin/sizer -v

===============================================================




Bugs

Operating Systems Analyst for unix systems
Humboldt State Univ.	Information Technology Services
Arcata, Calif.

email [email protected]

Bugs

Operating Systems Analyst for unix systems
Humboldt State Univ.	Information Technology Services
Arcata, Calif.

email [email protected]