Patch-ID# 101966-01 Keywords: window front swap wabifs drivers 2.4 large space readdir motif Synopsis: Wwabi 1.1: Wabi jumbo patch for i386 Date: Aug/17/94 Solaris Release: 2.x SunOS Release: 5.x Unbundled Product: Wabi Unbundled Release: 1.1 Xref: See patch 101858 for sparc architecture Relevant Architectures: i386 BugId's fixed with this patch: 1169917 1170232 1170260 1161954 1165501 1163540 1161952 1172643 1169743 1153114 1158682 1149888 1146113 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: /usr/lib/rmmount/action_wabi.so.1 SUNWwabi/drvr/wabi.sparc.5.4.o (sparc architecture only) SUNWwabi/drvr/wabi.intel.5.4.o (i386 architecture only) SUNWwabi/bin/wabi SUNWwabi/bin/wabiprog SUNWwabi/bin/wabifs (i386 architecture only) SUNWwabi/lib/locale/de/wabi/wabi_kb Problem Description: 1169917, Floppy disk eject (Meta+E) can cause processes related to Wabi, including entire OpenWindows desktop, to exit 1170232, swap space becomes exhausted because of "wabifs" processes that never terminated 1170260, Wabi Windows always stay where they first appeared (usually front) in stacking order with Motif Window Manager 1161954, No Wabi kernel drivers available for use with Solaris 2.4/SunOS 5.4; hence file sharing requests never actually checked, and no interaction with Volume Manager so floppy drive is unusable from Wabi 1165501, Run out of space with message "Table 7 Overflow" after repeated displays of large complex colored screens 1163450, Run out of space when cutting/pasting very large section of very large spreadsheet 1161952, Sometimes loop on soft failure from readdir(), typical symptom is inability to re-install a particular app over top of the copy that's already installed 1172643, Wabi under Solaris 2.4 x86 would always report "device not ready" to all attempts to use the floppy drive even with the correct kernel driver and volmgr interaction dynamic library 1169743, Wabi's entry in /etc/rmmount.conf wasn't at the left margin, contained an extraneous version identifier, and could occur multiple times (which could degrade performance for other apps desiring floppy access) 1153114, local version of `uname` command in path ahead of standard version would confuse Wabi client installation configuration and startup 1158682, Because of the change to the `df` command in Solaris 2.4, Wabi would sometimes incorrectly report not enough disk space to start, usually on the first invocation 1149888, Wabi will not run under Solaris x86 if LD_LIBRARY_PATH is not set 1146113, Wabi assumed hardware page size was 4K and would not run if the actual page size was different (which it was on 3xx systems, some Solbourne systems, etc.) Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- NOTE: The new Wabi kernel drivers for Solaris 2.4 were built using the pre-release versions of Solaris 2.4 that were available in June. It's expected they will continue to work without change on Solaris 2.4 FCS versions when they become available. NOTE: If you cannot access the serial communications ports on your machine from Wabi (or even see them from ConfigurationManager:Ports), check their permissions. Particularly on Solaris 2.4 systems, the permissions may not allow Wabi to access the ports. If the permissions don't allow Wabi access (ex: -rw-------), as root use chmod to give Wabi access (ex: -rw-rw-rw-). NOTE: After this patch is applied Wabi's auxiliary font server process will be more heavily used. This heavier use of the font server may expose latent bugs in your X-server. If Wabi windows start misbehaving right after you install this patch --particularly if the next thing they should do is draw some text in a font that hasn't been used before-- try disabling Wabi's use of the auxiliary font server process. To do this, edit $WABIHOME/lib/wabifs.displays, and comment out the line corresponding to your display. If Wabi's behavior doesn't improve, re-enable Wabi's use of its auxiliary font server process since it can noticeably improve Wabi performance. Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing:
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Any previously installed packages
in the patch should have been removed. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Patch Installation Messages:
---------------------------
Note: the messages listed below are not necessarily considered errors
as indicated in the explanations given. These messages are, however,
recorded in the patch installation log for diagnostic reference.
Message:
Package not patched:
PKG=SUNxxxx
Original package not installed
Explanation: One of the components of the patch would have patched a
package that is not installed on your system. This is not
necessarily an error. A Patch may fix a related bug for several
packages. Example: suppose a patch fixes a bug in both the
online-backup and fddi packages. If you had online-backup installed
but didn't have fddi installed, you would get the message
Package not patched:
PKG=SUNWbf
Original package not installed
This message only indicates an error if you thought the package
was installed on your system. If this is the case, take the
necessary action to install the package, backout the patch (if
it installed other packages) and re-install the patch.
Message:
Package not patched:
PKG=SUNxxx
ARCH=xxxxxxx
VERSION=xxxxxxx
Architecture mismatch
Explanation: One of the components of the patch would have patched a
package for an architecture different from your system. This is not
necessarily an error. Any patch to one of the architecture specific
packages may contain one element for each of the possible
architectures. For example, Assume you are running on a sun4m. If
you were to install a patch to package SUNWcar, you would see the
following (or similar) messages:
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4c
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4d
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4e
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
The only time these messages indicate an error condition
is if installpatch does not correctly recognize your architecture.
Message:
Package not patched:
PKG=SUNxxxx
ARCH=xxxx
VERSION=xxxxxxx
Version mismatch
Explanation: The version of software to which the patch is applied is
not installed on your system. For example, if you were running Solaris
5.3, and you tried to install a patch against Solaris 5.2, you would
see the following (or similar) message:
Package not patched:
PKG=SUNWcsu
ARCH=sparc
VERSION=10.0.2
Version mismatch
This message does not necessarily indicate an error. If
the version mismatch was for a package you needed patched, either
get the correct patch version or install the correct package version.
Then backout the patch (if necessary) and re-apply.
Patch Backout Errors:
---------------------
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: The user has attempted to back
out a patch that was never applied to this system. It is
possible that the patch was applied, but that the patch
directory /var/sadm/patch/ was deleted somehow.
If this is the case, the patch cannot be backed out. The
user may have to restore the original files from the
initial installation CD.
Error message:
This patch was obsoleted by patch $1.
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: The obsoleted contents of an
older patch rev that apparently still exists under /var/sadm/patch
should never be restored out of sequence. This could undermine
the integrity of the more current patch rev installed and the
restoration of the files it has saved.
Error message:
Patch was installed without backing up the original
files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used. The
original files can only be recovered from the original
installation CD.
Error message:
pkgrm of package failed return code .
See /var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file for the reason for
failure. Correct the problem and run the backout script again.
Error message:
Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
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 instructions above for
applying patches to a client.
A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
could 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