Patch-ID# 103341-01
Keywords: href interface pci igs ibm prtconf ifconfig plumb
Synopsis: Allows igs to find interfaces which prtconf misses in Solaris 2.5
Date: Apr/01/96
Solaris Release: 2.5, 2.5.1
SunOS Release:
Unbundled Product: Internet Gateway for Solaris (IGS 1.0)
Unbundled Release: 1.0
Relevant Architectures: x86
BugId's fixed with this patch: 1236410
Changes incorporated in this version:
Patches accumulated and obsoleted by this patch:
Patches which conflict with this patch:
Patches required with this patch:
Obsoleted by:
Files included with this patch:
interface.href
Problem Description:
1236410 IGS can not find interfaces of PCI on Solaris 2.5
Fixes the problem where prtconf doesn't report PCI interfaces
on Solaris 2.5. Other new interfaces also were added.
Patch Installation Instructions:
--------------------------------
Refer to the Install.info file for instructions on using the
generic 'installpatch' and 'backoutpatch' scripts provided with
each patch. Any other special or non-generic installation
instructions should be described below as special instructions.
Special Install Instructions:
-----------------------------
None.
Patch Installation Instructions:
--------------------------------
Instructions to install patch using "installpatch"
--------------------------------------------------
1. Become super-user.
2. Apply the patch by typing:
installpatch
where is the directory containing installpatch, and
is the directory containing the patch itself.
Example:
# cd /tmp/123456-01
# ./installpatch .
3. If any errors are reported, see "Patch Installation Errors" in
the Command Descriptions section below.
Rebooting the system or restarting the application after a successful
patch installation is usually necessary to utilize patch.
NOTE: On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See the next section for instructions
for installing a patch on a client.
Instructions for installing a patch and saving the backout data
to location other than the default save directory
--------------------------------------------------------------------
1. Become super-user.
2. Apply the patch by typing.
installpatch -B
where is the user specified directory
to save the backout data.
Instructions for installing a patch on a dataless client
--------------------------------------------------------------------
1. Before applying the patch, the following command must be executed
on the server to give the client read-only, root access to the
exported /usr file system so that the client can execute the
pkgadd command:
share -F nfs -o ro,anon=0 /export/exec//usr
The command:
share -F nfs -o ro,root= \
/export/exec//usr
accomplishes the same goal, but only gives root access to the
client specified in the command.
2. Login to the client system and become super-user.
3. Continue with step 2 in the "Instructions to install patch using
installpatch" section above.
Instructions for installing a patch on a diskless client
--------------------------------------------------------------------
To install a patch on a diskless client, you may either follow the
instructions for installing on a dataless client (that is, you may
logon to the client and install the patch), or you may use the
following instructions to install the patch while on the server.
1. Find the complete path for the root directory of the diskless
client.
2. Install the patch normally, but add the command option -R
to the command line. should be the completely specified.
Example:
# cd /tmp/123456-01
# ./installpatch -R /export/root/client1 .
Instructions for backing out a patch using "backoutpatch"
-----------------------------------------------------------
1. Become super-user.
2. Change directory to /var/sadm/patch:
cd /var/sadm/patch
3. Backout patch by typing:
/backoutpatch
where is the patch number.
Example:
# cd /var/sadm/patch
# 123456-01/backoutpatch 123456-01
4. If any errors are reported, see "Patch Backout Errors" in
the Command Descriptions section below.
Instructions for backing out a patch where the backout data was
saved to a directory other than the default location
--------------------------------------------------------------------
1. Follow steps 1 thru 4 above
2. If the backout data was moved, supply backoutpatch with the
new location of the backout data.
/backoutpatch -B
Instructions for backing out a patch on a dataless client
----------------------------------------------------------
1. Give the client root access to /usr as specified in the installpatch
section.
2. Logon to the client and follow backoutpatch instructions as
specified above.
Instructions for backing out a patch on a diskless client
-----------------------------------------------------------
To backout a patch on a diskless client, you may either follow the
instructions for backout on a dataless client (that is, you may
logon to the client and backout the patch), or you may use the
following instructions to backout the patch while on the server.
1. Find the complete path for the root directory of the diskless
client.
2. Backout the patch normally, but add the command option -R
to the command line. should be the completely specified.
Example:
# cd /export/root/client1/var/sadm/patch
# ./123456-01/backoutpatch -R /export/root/client1 123456-01
Instructions for identifying patches installed on system:
----------------------------------------------------------
Patch packets that have been installed can be identified by
using the -p option. To find out which patches are installed on
a diskless client, use both the -R option and the -p
option, where is the fully specified path to the client's
root directory.
#cd /tmp/123456-01
#./installpatch -p
#./installpatch -R /export/root/client1 -p
Also note that the command "showrev -p" will show the patches installed
on the local machine, but will not show patches installed on clients.
Command Descriptions
--------------------
NAME
installpatch - apply patch package to Solaris 2.x system
backoutpatch - remove patch package, restore previously saved files
SYNOPSIS
installpatch [-udpV] [-R ] [-B ] [-S ]
backoutpatch [-fV] [-R ] [-B ] [-S ]
DESCRIPTION
These installation and backout utilities apply only to
Solaris 2.x associated patches. They do not apply to Solaris
1.x associated patches. These utilities are currently only
provided with each patch package and are not included with
the standard Solaris 2.x release software.
OPTIONS
installpatch:
-u unconditional install, turns off file validation. Allows
the patch to be applied even if some of the files to be
patched have been modified since original installation.
-d Don't back up the files to be patched. This means
that the patch CANNOT BE BACKED OUT.
-p Print a list of the patches currently applied
-V Print script version number
-R
Define the full path name of a subdirectory to use as the
root_path. All package system information files are assumed
to be located in a directory tree starting in the
specified root_path. All patch files generated from the
installpatch will be located in the same directory tree.
Cannot be specified with the -S option.
-B Save backout data to a location other than the default
-S
Specify an alternate service (e.g. Solaris_2.3) for
patch package processing references. Cannot be speould affect the reliability of installpatch or backoutpatch
which uses package utilities to install and backout the patch
package. It is recommended that any patch that fixes package
utility problems be reviewed and, if necessary, applied before
other patches are applied. Such existing patches are:
100901 Solaris 2.1
101122 Solaris 2.2
101331 Solaris 2.3
SEE ALSO
pkgadd, pkgchk, pkgrm, pkginfo, showrev, cpio