From: Reed, Judith (jreed@navisite.com)
Date: Tue Apr 05 2005 - 09:34:53 EDT
I had asked how to combine a group of patches for Tru64v5.1A PK6 into a more compact operation. I rec'd several responses asking for a summary, and a couple (appended at end) with suggestions. Thanks to those who responded.
In the end, here's what we did:
1. Determine which ones of the group supersede others, and use most recent patch.
2. Determine if any patches patch the same files - after step one, none did, so no need to reboot between based on this.
3. Determine which want to rebuild kernel. Several did, but they weren't changing files which would affect the running system, thus we could postpone reboot to end
4. Make sure nothing would change the running system - nothing did.
5. Do all with command line dupatch with appropriate switches, omit kernel rebuilds and boots.
6. At end, rebuild kernel once, then reboot.
This made it reasonably easy to do them.
Here's the dupatch command we used:
./dupatch -install -kit ./ -name [name] -note . -patch all -noauto -proceed -product all
Alan Davis responded to my query:
If they are in dupatch format I usually do a fairly simple script that installs each one using the command-line syntax of dupatch. If there are reboots required I put a script in /sbin/rc3.d that will call the script at the end of the boot sequence. The install script chmod's itself when the last patch installs so it's no longer executable.
Dr. Tom Blinn responded:
If they were released as separate patch kits, you can either do
the install sequentially but (in most cases, and depending on
the content) defer the reboot until the end (usually you have
to reboot if you've built a new kernel, and you can usually do
the kernel rebuild once after loading all the patches that have
new kernel modules). But if any of the patches really do have
a dependency on a hard reboot after an earlier patch was put
on the system, you'd have to discover this and cope with it.
Otherwise, you would have to ask us (HP) to build you a patch
kit that has all the content in a single kit. It's possible
for us to do this, but it's a complicated process and a bit
error prone, and if you don't really need it done, you'd be
better off not asking for it. If the patches are ones that
you downloaded from the public web sites and not a set of kit
changes that you got in response to problem reports (what we
call Customer Specific Patches) then I doubt you'd get very
far asking to have a combined kit built.
Long term, your best bet is to get to V5.1B with the current
patch kit (whatever that is at the time), because as far as
I know (and I'm in a position to know), there are no plans to
ever release a new consolidated patch kit for V5.1A with all
the patch content since the last kit (which you already have).
Regards;
Judith Reed
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:17 EDT