Summary: Tru64 4.0F PK8 - dependencies

• Previous message: Dermot Paikkos: "Backup software advice"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Wed, 24 Sep 2003 14:36:00 +0100
To: "'tru64-unix-managers@ornl.gov'" <tru64-unix-managers@ornl.gov>

 Well, many thanks to those who replied - Sheila Hollenbaugh, Johan Brusche,
Matthew Wild,
Iain Barker, Bob Vickers and Harvey Rarback.

The general concensus is that - yes, you have to first remove previous
standard issue patches
that overlap with those in the kit.

 Johan Brusche from HP explained the steps needed before installing an
aggregate kit as follows:

1) Run "dupatch -track -type kit" , look for any kits that have "-E-" or
"-ES-"
    in their kitname and use dupatch "delete patch" to remove patches
from these
    kits.
    Example:
             T64V51AB3-C0043701-15279-ES-20020828 OSF520
             T64V51AB3-C0045704-15383-ES-20020906 OSF520
             T64V51AB3-C0055902-16064-ES-20021114 OSF520
             T64V51AB3-C0065801-15605-ES-20021001 OSF520
 
2) Run "dupatch -track -type patch" , and look for any patches that have
a "C " in front
    of their patch-id. Such are patches delivered by engineering as
solution for issues that have
    been escalated via IPMT and must also be removed.(Customer Specific
Patch or CSP )
 
    Example:
    Patch C 00973.00 - Avoid AdvFS mcell truncation on multi-volume
domains
 
3) Run dupatch baseline verification (item 5 in dupatch menu) and
authorize overwriting
   of any unknown origin files.
 
 
After installation of the patchkit, check the recent
/var/adm/patch/log/session.log*
files for any patch that might have been skipped from installation, due
do existing
file conflicts. Try to resolve the file conflict and rerun dupatch to
install the skipped patch(es).
 
If a patch installation conflict cannot be cleared, please report this
immediately to our
Tru64 UNIX support group and/or ask the customer to register a case.
 
Excluding patches from installation is only valid if the concerned
product is not
installed on the system, or if the patch itself is known to cause new
problems.

_________________________________________

Bob Vickers described a rather different approach - but do note his warning
at the end:

(1) Run the check-only installation and get a list of
files that were installed by so-called CSPs.

(2) Corrupt these files, for example by appending them with a space
character (you can't do this for shared libraries, try renaming them
instead).

(3) now run the baselining utility

(4) install the patch kit

This of course is an evil procedure which you do at your own risk but I
went through it and lived to tell the tale. I've attached a script which
helps find the relevant files for you.

____________________________________________________________________________
____________

I have yet to go through a second attempt to install this kit, but hope to
do so soon. I'll summarise if there are any problems.

Again thanks to everyone,

  Lindsay

**************************************************************************

Now exhibiting at the British Library Galleries:

Painted Labyrinth : the world of the Lindisfarne Gospels

Until 28 September 2003. Admission Free.

*************************************************************************

The information contained in this e-mail is confidential and may be legally
privileged. It is intended for the addressee(s) only. If you are not the
intended recipient, please delete this e-mail and notify the
postmaster@bl.uk : The contents of this e-mail must not be disclosed or
copied without the sender's consent.

The statements and opinions expressed in this message are those of the
author and do not necessarily reflect those of the British Library. The
British Library does not take any responsibility for the views of the
author.

*************************************************************************

• Previous message: Dermot Paikkos: "Backup software advice"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]