Installing Patch Kit

[Paolo_R]

Having installed Tru64 UNIX 5.1B in a virtual environment, I'm trying to install Patch Kit V.4. I've mounted the CD-ROM called Tru64_UNIX-5.1B_-_Patch_Kit.iso. This has a folder structure as follows: patch_kit then patch_tools (folder) SYSCHECK133.KIT (folder) Tru64_UNIX_V5.1B (folder) dupatch and one or two documents. I changed directory to patch_kit and ran ./dupatch. I get a message 'Enter patch to the top of the patch distribution or enter q to quit'. I've changed directory to each of the sub-directories and run dupatch and keep getting the message: ' -directory name-does not contain any Tru64 UNIX setld format patch kit'. None of the files in the sub-folders is a .tar file. They all seem to be of the form OSFPAT02500100540 etc. with no file extension. Help please! Where do I find the appropriately formatted patch kit? Thanks Paul

[Steven Schweda]

> [...] I'm trying to install Patch Kit V.4. I've mounted the CD-ROM
> called Tru64_UNIX-5.1B_-_Patch_Kit.iso.

   How do we know that that disc image contains the (correct) patch kit?

> This has a folder structure as follows: [...]

   Rather than write a long, free-format book, why not copy+paste some
appropriate "ls" output?  Show me; don't tell me.

> [...] and one or two documents.

   Is one of those "one or two documents" the patch-kit installation
instructions?

> [...] I get a message 'Enter patch to the top of the patch
> distribution or enter q to quit'.

   Ok.  And what answer did you give it?  Note that copy+paste might
have spelled "Enter patch" differently.  Copy+paste is your friend.

   I haven't done this for years, and I started with a downloaded kit
rather than a CD image, so I know nothing, but my dim recollection is
that this was pretty easy if you followed the instructions.

[Paolo_R]

Steven # pwd

/cdrom/patch_kit

# ls 00-READ-ME-FIRST

PatchInstallGuide.pdf

TruCluster_V5.1B I18N_UNIX_V5.1B

PatchInstallGuide.txt

dupatch

PatchInstallGuide

SYSCHECK133.kit

patch_tools

PatchInstallGuide.htm

Tru64_UNIX_V5.1B #

PatchInstallGuide.htm gives a lot of info about what you can and can't do with dupatch. It doesn't indicate if dupatch has to be 'pointed' at any particular folder or file.

>>> [...] I get a message 'Enter patch to the top of the patch > distribution or enter q to quit'.<<

I obviously misunderstood this. When I entered Tru64_UNIX_V5.1B dupatch loaded and gave me the following. I have only a single-user mode set up so I don't understand why it keeps looping round with the 'single user' message.

>> This operation can be performed in single-user mode only.

Tru64 UNIX Patch Utility (Rev. 46-00) ========================== -

This dupatch session is logged in /var/adm/patch/log/session.log

Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: 1

Tru64 UNIX Patch Utility (Rev. 46-00) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Patch Installation Menu: ----------------------- 1) Pre-Installation Check ONLY 2) Check & Install patches in Single-User Mode 3) Check & Install in Multi-User mode b) Back to Main Menu q) Quit Enter your choice: 2

This operation can be performed in single-user mode only. Tru64 UNIX Patch Utility (Rev. 46-00) ========================== - This dupatch session is logged in /var/adm/patch/log/session.log Main Menu: --------- 1) Patch Installation 2) Patch Deletion 3) Patch Documentation 4) Patch Tracking 5) Patch Baseline Analysis/Adjustment h) Help on Command Line Interface q) Quit Enter your choice: q <<

I'm not sure where to go from here. Thanks Paul

[Paolo_R]

OK, I managed to boot into single-user mode (set boot_osflags S). When I tried to run dupatch I get: './dupatch: /usr/share/lib/shell/libscp : not found'. Can you offer any advice? Paul

[Paolo_R]

After further searching I ran bcheckrc which apparently allows use of LSM in single-user mode. This allows dupatch to bring up its menu. Having chosen 'Check and Install Patches in Single-User Mode' I then get a message 'OSF.image file not found in patch kit ... exiting'. So it appears I'm stuffed. Paul

[Steven Schweda]

> [...] I'm trying to install Patch Kit V.4. I've mounted the CD-ROM
> called Tru64_UNIX-5.1B_-_Patch_Kit.iso.

   Thanks to a recent power-supply failure, I couldn't get to much of my
Tru64 info, but my misery may be your joy.  I just installed V5.1B-4 on
my long-disused PWS 500au (with a live power supply), followed by the
patch kit on the CD-ROM (mis-)labeled as follows:

--------
                        HP Tru64 UNIX
                           V5.1B-3

      Version 5.1B-4
--------

   Mine seems to be newer than yours, but this stuff has been changing
so slowly that any differences between mine and yours should be very
small:

# ls -l /cdrom/patch_kit
total 120
-rw-rw-r--   1 root     system      1221 Nov 14  2005 00-READ-ME-FIRST
drwxr-xr-x   4 bin      bin         2048 Dec  8  2006 I18N_UNIX_V5.1B
drwxr-xr-x   6 bin      bin         2048 Dec  8  2006 PatchInstallGuide
-rw-r--r--   1 bin      bin          107 Dec  8  2006 PatchInstallGuide.htm
lrwxrwxrwx   1 root     system        43 Dec  8  2006 PatchInstallGuide.pdf ->
 PatchInstallGuide/pdf/PatchInstallGuide.pdf
lrwxrwxrwx   1 root     system        43 Dec  8  2006 PatchInstallGuide.txt ->
 PatchInstallGuide/txt/PatchInstallGuide.txt
drwxr-xr-x   3 root     bin         2048 Dec  8  2006 SYSCHECK143.kit
drwxr-xr-x   4 bin      bin         2048 Dec  8  2006 Tru64_UNIX_V5.1B
drwxr-xr-x   4 bin      bin         2048 Dec  8  2006 TruCluster_V5.1B
drwxr-xr-x   3 bin      bin         2048 Nov 24  2006 clone_tools
-rwxr-xr-x   1 bin      bin        59963 Nov 24  2006 dupatch
-rwxr-xr-x   1 bin      bin        18430 Nov 24  2006 dupclone
-r-xr-xr-x   1 bin      bin        19284 Nov 24  2006 license.txt
drwxr-xr-x   3 bin      bin         2048 Dec  8  2006 patch_tools
#

> [...] I get a message 'Enter patch to the top of the patch
> distribution or enter q to quit'.

   The actual question was:

      Enter path to the top of the patch distribution,
      or enter "q" to quit :

   Note "Enter PATH", not "Enter PATCH".

> [...] Copy+paste is your friend.

   Still true.  When you want to report problems like this, it's
important to show exactly what you did, and exactly what happened when
you did it.  Copy+paste showing the actual queries and your actual
responses is much more useful than incomplete/vague descriptions of what
you were trying to do, or what you think it all means.

> I obviously misunderstood this. When I entered Tru64_UNIX_V5.1B dupatch
> loaded and gave me the following. I have only a single-user mode set up
> so I don't understand why it keeps looping round with the 'single user'
> message.

   "single-user mode" is a UNIX technical term (different from
"multi-user mode)", and does not refer to the fact that "root" is your
only user.

> OK, I managed to boot into single-user mode (set boot_osflags S).
> [...]

   You're working too hard.  You shouldn't need to worry about this.
Let dupatch worry about it.  Run dupatch from normal, multi-user mode.
After you answer some questions, dupatch should get to a point like
this:

   *** The Patch Kit will install 71 patches ***

************************** CAUTION ************************************

        Interruption of this phase of the operation will corrupt your
        operating system software and compromise the patch database
        integrity.

        DO NOT Ctrl/C, power off your system, or in any other way
        interrupt the patch operation. The patch operation is complete
        when you are returned to the Patch Utility menus.

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

This will bring the system down to single-user mode.
Do you wish to continue? [y]:


      [Answer "y", and dupatch should do what it says, and then it
      should start installing the patches.

      In my case:

         # pwd
         /cdrom/patch_kit

      so a correct answer was "."  (But I suspect that
      "/cdrom/patch_kit" would have worked, too.  If you mounted your
      CD-ROM at some other place, then make adjustments as needed.)]

# ./dupatch

Enter path to the top of the patch distribution,
or enter "q" to quit : .        <---[ _PATH_ to the patch kit. ]

        * A new version of patch tools required for patch management
          is now being installed on your system.

        * Tools updated, invoking the updated Patch Utility...  

Tru64 UNIX Patch Utility (Rev. 52-00)
==========================
        - This dupatch session is logged in /var/adm/patch/log/session.log

    Main Menu:
    ---------

    1)  Patch Installation
    2)  Patch Deletion
    3)  Patch Documentation
    
    4)  Patch Tracking
    5)  Patch Baseline Analysis/Adjustment
    
    h)  Help on Command Line Interface
    
    q)  Quit

Enter your choice: 1

 Tru64 UNIX Patch Utility (Rev. 52-00)
 ==========================
         - This dupatch session is logged in /var/adm/patch/log/session.log

     Patch Installation Menu:
     -----------------------

    1)  Pre-Installation Check ONLY
    2)  Check & Install in single-user mode w/ network services
    3)  Check & Install in Multi-User mode
    
    b)  Back to Main Menu
    q)  Quit

Enter your choice: 2

[Note that "w/ network services" is good, because it means that you can
do this from a remote terminal, which means that, if you have a terminal
emulator which can record a transcript of what happens in this session,
then you can copy+paste the bad news here more easily.)

[... Long license text ...]

To read the license again, type 'license'.
Do you accept the license agreement? (y/n) : y

Checking patch kit for transmission errors during download...

Finished Checking patch kit checksums

Gathering patch information...
  (depending upon the size of the patch kit, this may take awhile)

[... much work ...]

        A reboot is necessary to complete the patch installation. Do
        you want to reboot now? [y/n] [y]: y

Existing kernel copied to /vmunix.PrePatch.

New Kernel (/sys/PURT/vmunix) copied to /vmunix.

    *** successfully installed 71 patches; failed to install 0 patches ***

   * A system reboot of the patched system is required for the
 successfully installed patches.

rlogin: connection closed
pro3$

   Then it reboots, and everyone's happy.

   As I said, for me, it was pretty easy if you followed the
instructions.


   When it was all over:

# /usr/sbin/dupatch -track -type patch_level | grep -i 'patch kit'
Gathering details of relevant patch kits...
Patch Kit 6: T64V51BB27AS0006-20061208 IOS540
Patch Kit 6: T64V51BB27AS0006-20061208 OSF540

So, apparently, "5.1B-4" means "Patch Kit 6".


> After further searching I ran bcheckrc which apparently allows use of
> LSM in single-user mode.

   Working too hard again.  See "working too hard" above.

[Paolo_R]

Steven

Here is a cut'n'paste of another attempt to install the Patch Kit - I
get exactly the same message as before (about needing to be in
single-user mode):


# mount -t cdfs -o noversion /dev/disk/cdrom0c /cdrom
# cd /cdrom
# ls
patch_kit
# cd patch_kit
# ls -l
total 70
-rw-r--r--   1 bin      bin         1219 Nov 26  2003 00-READ-ME-FIRST
drwxr-xr-x   4 bin      bin         2048 Jun 17  2004 I18N_UNIX_V5.1B
drwxr-xr-x   6 bin      bin         2048 Jun 17  2004 PatchInstallGuide
-rw-r--r--   1 bin      bin          106 Jun 26  2004 PatchInstallGuide.htm
lrwxr-xr-x   1 root     bin           43 Jun 26  2004
PatchInstallGuide.pdf -> PatchInstallGuide/pdf/PatchInstallGuide.pdf
lrwxr-xr-x   1 root     bin           43 Jun 26  2004
PatchInstallGuide.txt -> PatchInstallGuide/txt/PatchInstallGuide.txt
drwxr-xr-x   3 bin      bin         2048 Jun 17  2004 SYSCHECK133.kit
drwxr-xr-x   4 bin      bin         2048 Jun 17  2004 Tru64_UNIX_V5.1B
drwxr-xr-x   4 bin      bin         2048 Jun 17  2004 TruCluster_V5.1B
-rwxr-xr-x   1 bin      bin        59022 Jun  8  2004 dupatch
drwxr-xr-x   3 bin      bin         2048 Jun 17  2004 patch_tools
# ./dupatch

Enter path to the top of the patch distribution,
or enter "q" to quit : Tru64_UNIX_V5.1B

        * Previous session logs saved in session.log.[1-25]



This is a new style patch kit, which differs from earlier Tru64 UNIX
patch kits in several ways:

  - You can no longer install or remove individual patches;
    instead, you can only install or remove all of the
    patches in this kit.

  - The time to install the patch kit is substantially faster.

  - The list of patches displayed by the dupatch utility
    has different look.

See the "Patch Summary and Release Notes" and the "Patch Kit
Installation Instructions" for more detailed information.


Tru64 UNIX Patch Utility (Rev. 46-00)
==========================
        - This dupatch session is logged in /var/adm/patch/log/session.log

    Main Menu:
    ---------

    1)  Patch Installation
    2)  Patch Deletion
    3)  Patch Documentation

    4)  Patch Tracking
    5)  Patch Baseline Analysis/Adjustment

    h)  Help on Command Line Interface

    q)  Quit

Enter your choice: 1

 Tru64 UNIX Patch Utility (Rev. 46-00)
 ==========================
         - This dupatch session is logged in /var/adm/patch/log/session.log

     Patch Installation Menu:
     -----------------------

    1)  Pre-Installation Check ONLY
    2)  Check & Install patches in Single-User Mode
    3)  Check & Install in Multi-User mode

    b)  Back to Main Menu
    q)  Quit

Enter your choice: 2

*This operation can be performed in single-user mode only.*

Tru64 UNIX Patch Utility (Rev. 46-00)
==========================
        - This dupatch session is logged in /var/adm/patch/log/session.log

    Main Menu:
    ---------

    1)  Patch Installation
    2)  Patch Deletion
    3)  Patch Documentation

    4)  Patch Tracking
    5)  Patch Baseline Analysis/Adjustment

    h)  Help on Command Line Interface

    q)  Quit

*so I tried installing using Option 3: *

Enter your choice:

Tru64 UNIX Patch Utility (Rev. 46-00)
 ==========================
         - This dupatch session is logged in /var/adm/patch/log/session.log

     Patch Installation Menu:
     -----------------------

    1)  Pre-Installation Check ONLY
    2)  Check & Install patches in Single-User Mode
    3)  Check & Install in Multi-User mode

    b)  Back to Main Menu
    q)  Quit

Enter your choice: 3

                *** Installation Warning ***

You have chosen to install patches onto this system while it is running in
Multi-User mode. Some patches may directly affect core operating system
operations. To ensure the proper operation of all applications, it is
strongly suggested that you install these patches while the system is in
Single-User mode. If this cannot be done, install these patches when the
system is as lightly loaded as possible (i.e. not running production
environments, no users logged on, etc.).

Do you wish to continue? (y/n) [y]: y

Checking patch kit for transmission errors during download...
/cdrom/patch_kit/Tru64_UNIX_V5.1B/../kit: No such file or directory


OSF.image file not found in patch kit.  Your Patch may
be incomplete.  Please resolve the problem prior to installing patches. 
Exiting...

*This is the content of **/cdrom/patch_kit/Tru64_UNIX_V5.1B/../kit*

# ls kit
INSTCTRL                OSFPAT02503400540       OSFPAT02507200540
ManualPatchInformation  OSFPAT02503500540       OSFPAT02507300540
OSFPAT02500100540       OSFPAT02503600540       OSFPAT02507500540
OSFPAT02500200540       OSFPAT02503800540       OSFPAT02507700540
OSFPAT02500300540       OSFPAT02503900540       OSFPAT02507900540
OSFPAT02500700540       OSFPAT02504500540       OSFPAT02508000540
OSFPAT02500900540       OSFPAT02504600540       OSFPAT02508400540
OSFPAT02501000540       OSFPAT02504700540       OSFPAT02508500540
OSFPAT02501100540       OSFPAT02504800540       OSFPAT02508600540
OSFPAT02501200540       OSFPAT02504900540       OSFPAT02508900540
OSFPAT02501300540       OSFPAT02505000540       OSFPAT02509400540
OSFPAT02501400540       OSFPAT02505100540       OSFPAT02509500540
OSFPAT02501500540       OSFPAT02505200540       OSFPAT02510000540
OSFPAT02501600540       OSFPAT02505300540       OSFPAT02510200540
OSFPAT02501900540       OSFPAT02505400540       OSFPAT02510600540
OSFPAT02502000540       OSFPAT02505500540       OSFPAT02510700540
OSFPAT02502100540       OSFPAT02506000540       OSFPAT02511000540
OSFPAT02502200540       OSFPAT02506200540       OSFPAT02511300540
OSFPAT02502300540       OSFPAT02506400540       OSFPAT02511400540
OSFPAT02502600540       OSFPAT02506800540       OSFPAT02511500540
OSFPAT02502800540       OSFPAT02506900540       RCSIdInformation
OSFPAT02503000540       OSFPAT02507000540       instctrl
OSFPAT02503100540       OSFPAT02507100540       scp_extensions
#




---
This email has been checked for viruses by Avast antivirus software.

[Steven Schweda]

   I did:

# ./dupatch

Enter path to the top of the patch distribution,
or enter "q" to quit : .

   You did:

# ./dupatch

Enter path to the top of the patch distribution,
or enter "q" to quit : Tru64_UNIX_V5.1B

   Perhaps that difference is significant.  After that, unlike you, I
saw:

        * A new version of patch tools required for patch management
          is now being installed on your system.

        * Tools updated, invoking the updated Patch Utility...   

Tru64 UNIX Patch Utility (Rev. 52-00)
[...]

   I'd guess that that's because the "patch_tools" directory is
"./patch_tools", not "Tru64_UNIX_V5.1B/patch_tools", and "dupatch" is
looking for it at "the top of the patch distribution", which is "."
("/cdrom/patch_kit"), not "Tru64_UNIX_V5.1B"
("/cdrom/patch_kit/Tru64_UNIX_V5.1B").

   Without looking at the details, I'd guess that "dupatch" installs the
new patch tools if it finds them, and it's not finding yours, because
your "top" is not the real "top".  So you're trying to use some old,
left-over version of patch tools, instead of the new ones in your patch
kit.

[Paolo_R]

Steven: thanks to you I finally got to install the Patch Kit.

>>> I did: # ./dupatch

Enter path to the top of the patch distribution, or enter "q" to quit : .

You did:

# ./dupatch Enter path to the top of the patch distribution, or enter "q" to quit : Tru64_UNIX_V5.1B<<<

It seems hitting Enter after the message causes dupatch to find the appropriate programs to load - at least in my case. I note you entered '.'

>>>Gathering patch information... (depending upon the size of the patch kit, this may take awhile) [... much work ...]<<<

A slight understatement :-) It took about 6 hours on my virtual Alpha to complete the whole process to rebooting. Thanks once again.

Now, all I need to do is figure out how configure Tru64 UNIX to provide a CDE graphical interface - X-servers and all that :-)

Paul

[Steven Schweda]

   Glad to hear that you got it going.  (What could go wrong?)

> [...] It took about 6 hours on my virtual Alpha to complete the whole
> process to rebooting. [...]

   My notes are sloppy, but I thing that I sat at my Personal
Workstation 500au for an hour or two.

> Now, all I need to do is figure out how configure Tru64 UNIX to
> provide a CDE graphical interface - X-servers and all that :-)

   On my fresh installation (with an old ELSA GLoria Synergy card, an
old PS2 kewboard, and an old PS2 mouse), it all just started up.  If it
doesn't just happen for you, and your emulator has a suitable (emulated)
graphics card, then I'd probably start plowing through the official
Tru64 documentation.  If desperate, "man X" or "man -k dt".

   It should be educational.