AlphaServer SC patch kit:
==========================

AlphaServer SC Version :  SCV2.6 SSB
Kit Name: CSP 424.03/T64KIT0021691-V51BB24-20040223
Release Date: 7/Apr/04
PTR: 2-1405
IPMT Number: 106858
Abstract: V2.6 version of lsm.mod for PSC configuration


Description of Patch:
=====================
This kit provides a V2.6 version of the lsm.mod fix for slow boot times. 

This patch replaces patch T64KIT0021235-V51BB24-20040108, an earlier fix for the 
same problem.

Kit location:
=============
The patch kit is T64KIT0021691-V51BB24-20040223.tar and it can be downloaded from
ITRC.


Prerequisites:
==============
Before installing this Patch kit, you should ensure the following:

1) You have all mandatory patches for this release installed

2) You have the following specific patches installed:
<List all other specific patches that this patch depends on>


Kit checksum:
=============
# cksum T64KIT0021691-V51BB24-20040223.tar
871599563 4464640 T64KIT0021691-V51BB24-20040223.tar


Updated files:
==============

A list of the files included in this patch is given below
along with the cksum values for each file.

# cksum ./lsm.mod
2553510334 890506 ./lsm.mod



Instructions:
=============
This patch is provided as an sc_dupatch installable kit.  Unpack it
into a directory that is NFS mounted on all domains e.g.
/usr/cspkit and follow the following steps to install it:


Patch required on Management Server (if used) : YES / NO
Patch required on Domains                     : YES / NO


1) Verify that it is possible to install the patches as follows:

   On the Management Server (if used)

   #/usr/sbin/sc_dupatch -install -kit /usr/cspkit/patch_kit -name <user-name>
    -note  <user-note> -noroll -nolevel2 -noauto -precheck_only -patch all

   On Domains:

   # sra command -domains all -member 1 -command '/usr/sbin/sc_dupatch -install
     -kit /tmp/CSPkit/patch_kit -name <user-name> -note  <user-note> -noroll -nolevel2
     -noauto -precheck_only -patch C424.03'


       Note:
       ======
       if you encounter a message similiar to the following :
             ./sys/BINARY/nfs.mod:
                   its origin can not be identified.

       then,  you will need to run the actual installation (Step 3)
       with the " -deps_only " flag.

       For Example:

       # /usr/sbin/sc_dupatch -install -kit /tmp/CSPkit/patch_kit -name <user-name>
         -note <user-note> -noroll -nolevel2 -noauto -deps_only -patch all

       A full description of -deps_only is provided in Appendix A.1 below:
  
 

2) Now Run the Patch Installation as follows:


  On the Management Server (if Used):
  -----------------------------------

   Install the patch using the following commands:


   #/usr/sbin/sc_dupatch -install -kit /usr/cspkit/patch_kit -name <user-name>
    -note  <user-note> -noroll -nolevel2 -noauto -patch all

   Rebuild your kernel
   # doconfig -c HOSTNAME
   Copy the new kernel to /vmunix
   Reboot the machine
   # shutdown -r now


  On Domains:
  -----------
   Install the patch using the following commands:

   # sra command -domains all -member 1 -command '/usr/sbin/sc_dupatch -install
     -kit /tmp/CSPkit/patch_kit -name <user-name> -note  <user-note> -noroll -nolevel2
     -noauto -patch C424.03'

   Now Build and Deploy the Kernels:
   Make sure all nodes are up so that kernels will be built on all nodes

   # sra command -domains all -member 1 -command 'BuildKernels'
   # sra command -domains all -member 1 -command 'DeployKernels'

   Shutdown the Domains:
   # sra shutdown -domains all

   Now boot All nodes:
   # sra boot -domains all







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

Appendices:
===========

A.1 Details of -deps_only option
-------------------------------- 

Patches from UNIX support have previously been supplied to AlphaServer SC
customers in a manual install format. That is, patches were installed by the
customer running a script to copy the patch to the correct location. The
standard UNIX support patches for non-SC customers have always been supplied
using the CSP (Customer Specific Patch) format and are installed using the
dupatch tool. Patches for SC customers are now also being provided in CSP
format and these patches need to be installed using the sc_dupatch tool.

sc_dupatch does some dependency checking to ensure the patches already on the
machine are correct. It does this by comparing the chksums of files on the
system with its own dependency list. If you have manually installed a patch
that is on the dependency list for this new patch, then sc_dupatch will report
an error and not install the patch. That is because sc_dupatch is not aware of
patches installed manually.

If sc_dupatch reports an error indicating a failure to install one or more
patches, check whether this error message was generated by sc_dupatch detecting
a mismatch caused by the existence of a manually installed patch.

If you're satisfied that the conflict does arise from a manually-installed
patch which you want to override, then a simple workaround is available in the
form of the new deps_only switch. This has been introduced to cater
specifically for such situations. It turns off the inventory-checking mechanism
so that the pre-install checking is restricted to dependency-checking only.
Simply re-run the install command with the deps_only flag to skip this
inventory check and allow the installation to proceed.