This chapter provides instructions on how to install or upgrade to Solaris 7 3/99 system software on x86 platforms.
The Solaris 7 3/99 release provides:
New and updated device drivers to support new x86 hardware
New features as described in the supplemental documentation on the Solaris 7 documentation CD included with this product
The Solaris 7 Maintenance UpdateTM (MU) patches integrated in to the Solaris system software
For more information about the hardware requirements for this installation, see the documentation provided by the hardware manufacturer.
For more information about installation and how to use the new Solaris Product Registry, see Solaris 7 Installation Supplement.
The Solaris 7 (Intel Platform Edition) Hardware Compatibility List has changed since publication. The changes are included in Appendix B, Hardware Compatibility List for Solaris 7 (Intel Platform Edition) 3/99 of these Release Notes.
Before you install or upgrade to the Solaris 7 3/99 software, make sure that you back up your files. For information on backing up your system, see the System Administration Guide.
You can use the SolarisTM Web Start, JumpStartTM, Custom JumpStart, or Interactive installation method to install the Solaris 7 3/99 system software. 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.
When the installation is complete, check the following files.
To view the install_log, begin.log, and finish.log files:
# cd /var/sadm/system/logs |
Use an editor to check the files.
If you use Solaris 7 as an install server, you need to modify the Solaris 7 /etc/nsswitch.conf file before you run add_install_client.
Go to this line in the Solaris 7 /etc/nsswitch.conf file:
hosts: xfn nis [NOTFOUND=return] files |
Remove the xfn entry so that the line looks like this:
hosts: nis [NOTFOUND=return] files |
Run add_install_client from the Solaris 7 3/99 CD.
You need to install SolsticeTM AdminSuiteTM 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:
2.5.1: MU3, MU4, and MU5
2.6: MU1 and MU2
7: MU1
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.
For a list of new platforms and the options that are available for this release, see the hardware manufacturer's documentation.
If you are unable to obtain the patch from access1.sun.com, go through your normal support channel.
When the installation is complete, check the following files.
To view the install_log, begin.log, and finish.log files:
# cd /var/sadm/system/logs |
Use an editor to check the files.
Before upgrading, refer to the "Installation Bugs You Need to Know About Before the Start of an Upgrade" for important upgrade information.
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.
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...
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:
Any patches supplied as part of the Solaris 7 3/99 system software to be reapplied to your system. You will not be able to back out these patches.
Any patches previously installed on your system that are not included in the Solaris 7 3/99 system software to be removed.
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".
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.
If you are using the Interactive installation method to upgrade, choose the Analyze option to perform the analysis.
If you are not using the Interactive installation method to upgrade, use the steps below to perform the analysis using the analyze_patches script.
After performing the analysis, refer to "Reviewing the Patch Analyzer Output" for detailed information about the patch analysis results.
To run the analyze_patches script:
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.
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 |
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. |
After performing the analysis, use these steps to review the output.
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.
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.
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.
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...
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.
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:
2.5.1: MU3, MU4, and MU5
2.6: MU1 and MU2
7: MU1
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.
To identify the version of your Solaris 7 3/99 software:
# cat /etc/release |