test

Solaris 7 3/99 Release Notes (Intel Platform Edition)

Upgrading to Solaris 7 3/99 System Software

Before upgrading, refer to the "Installation Bugs You Need to Know About Before the Start of an Upgrade" for important upgrade information.

Upgrading From the Solaris 2.5.1 or 2.6 Operating Environment

To upgrade, use the JumpStart, Custom JumpStart, or Interactive installation method with the Upgrade option. For detailed instructions on installing Solaris software, see the publications Solaris 7 Installation Library and Solaris 7 Advanced Installation Guide on the Solaris 7 Documentation CD included with this product.

Note -

During an upgrade, you may receive an informational message regarding some of the packages (including SUNWolrte, SUNWoldcv, SUNWoldte, SUNWolaud). No action is required.

An example of this message is:

Doing pkgadd of SUNWolrte to /

This message indicates an attempt to install the same architecture and version of a package that is already installed.

Installation of SUNWolrte was successful...

Upgrading From the Solaris 7 Operating Environment

If you are already running the Solaris 7 operating environment and have installed patches, upgrading to the Solaris 7 3/99 system software will cause:

To see a list of patches that will be removed, use the Patch Analyzer as described below.

If you have not installed patches on your Solaris 7 system, go to "Upgrading to Solaris 7 3/99 System Software From the Solaris 7 Operating Environment".

Analyzing the Patches

The Patch Analyzer performs an analysis on your system to determine which (if any) patches will be removed by upgrading to the Solaris 7 3/99 operating environment. The Patch Analyzer is available as a script to run manually and as part of the Interactive installation method.

After performing the analysis, refer to "Reviewing the Patch Analyzer Output" for detailed information about the patch analysis results.

Running the analyze_patches Script

To run the analyze_patches script:

Note -

To run the analyze_patches script, the installed system and the Solaris 7 3/99 CD (or net image) must be accessible by the script either through an NFSTM mount or using locally mounted media.

  1. Change directories to the Misc directory on the OS image.

    • If the image is on locally mounted media, type:


      # cd /cdrom/sol_7_399_x86/s2/Solaris_2.7/Misc

    • If the image is available through an NFS mount, type:


      # cd /NFS_mount_directory/Solaris_2.7/Misc

  2. Run the analyze_patches script:


    # ./analyze_patches

    The options listed in Table 1-1 can be used on the command line.

    Table 1-1 Command-Line Options for analyze_patches

    Option 

    Description 

    -R rootdir

    rootdir is the root of the installed system. It defaults to /.

    -N netdir

    netdir is the path to the root of the OS image to be installed. It defaults to /cdrom/cdrom0. It should point to the directory containing the Solaris_2.7 directory. You must use this option if running the patch_analyzer from an NFS mount.

    -D databasedir

    If the script is invoked from a directory other than the /Misc directory on the OS image, the program will not find the database it uses for patch analysis. Use the -D option to supply the path to the database. Without this database, contained in the /Solaris_2.7/Misc/database on the OS image, the script will not work properly.

Reviewing the Patch Analyzer Output

After performing the analysis, use these steps to review the output.

  1. Review the output of the analyze_patches script.

    • The Patch Analyzer provides a list of patches that will be removed, downgraded, accumulated, or obsoleted by other patches. Patch accumulations are similar to patch upgrades. The accumulated patch is removed and its fixes are delivered by a new patch. Messages such as the following are shown:


      Patch 105644-03 will be removed.
Patch 105925 will be downgraded from -02 to -01.
Patch 105776-01 will be accumulated/obsoleted by patch 105181-05.

    • If the Patch Analyzer program does not provide a list, no action will be taken against any patches previously installed on your system.

  2. Decide if patch replacements and deletions are acceptable.

    • If the patch replacements and deletions by the Solaris 7 3/99 system software are acceptable, continue to the section "Upgrading to Solaris 7 3/99 System Software From the Solaris 7 Operating Environment."

    • If the patch replacements and deletions by the Solaris 7 3/99 system software are not acceptable, do not upgrade using the Solaris 7 3/99 CD. You may use the Solaris 7 MU1 CD and Solaris 7 Maintenance Update 1 Release Notes to install the patches on your Solaris 7 system.

Upgrading to Solaris 7 3/99 System Software From the Solaris 7 Operating Environment

To upgrade, use the JumpStart, Custom JumpStart, or Interactive installation method with the Upgrade option. For detailed instructions on installing Solaris software, see the publications Solaris 7 Installation Library and Solaris 7 Advanced Installation Guide on the Solaris 7 Documentation CD included with this product.

Note -

During an upgrade, you may receive an informational message regarding some of the packages (including SUNWolrte, SUNWoldcv, SUNWoldte, SUNWolaud). No action is required.

An example of this message is:

Doing pkgadd of SUNWolrte to /

This message indicates an attempt to install the same architecture and version of a package that is already installed.

Installation of SUNWolrte was successful...

Verifying the Upgrade

When the upgrade is complete, check the upgrade_log file to verify the installation: 


# cd /var/sadm/system/logs

Use an editor to check these files.

Updating Diskless Clients and AutoClients From a Server After an Upgrade

You need to install Solstice AdminSuite 2.3 patch number 104468-06 or any subsequent revision of this patch before you add OS services to your server. You will find the patch and installation instructions at http://access1.sun.com/private-cgi/patch2html?README.104468-06.

If you are using Solstice AdminSuite with a patched Solaris release in which it is inadvisable or impossible to remove all the patches, then you will need to have the following file to add OS services:

/var/sadm/patch/.mu_applied

This file is automatically created by the following MU releases:

Caution - Caution -

With this workaround, Solstice AdminSuite is unable to track all the patches in a system. Use admclientpatch to add or remove patches to or from the system.

If you are unable to obtain the patch from access1.sun.com, go through your normal support channel.

Identifying the Version of Your Solaris 7 3/99 Software

To identify the version of your Solaris 7 3/99 software: 


# cat /etc/release