Patch-ID# 101966-03 Keywords: window front swap wabifs drivers 2.4 large space readdir motif Synopsis: SUNWwabi 1.1 x86: Jumbo patch for i386 Date: Sep/30/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 1176539 1176540 Changes incorporated in this version: 1176539 1176540 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/wabifs.displays 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.) 1176539, Wabi sometimes hangs either itself or the entire desktop if an auxiliary font server process is not only running but actually doing something, as it may be after an earlier revision of patch 101966/101858 is applied 1176540, File sharing collisions are not detected if one of the file opens is of a local file on a system running Solaris 2.4 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: If you have modified $WABIHOME/lib/wabifs.displays, save a copy of it before installing this patch. This patch will overwrite any previous version of that file. (If you didn't save the file before installing this patch, you may find a copy of it somewhere under /var/sadm/patch/101966-03/save.) To restore desired parts of your local configuration, manually edit your changes into the new $WABIHOME/lib/wabifs.displays after you complete installation of this patch. NOTE: After this patch is applied configuration file $WABIHOME/lib/wabifs.displays will be changed so Wabi's default behavior is to not use an auxiliary font server process with most X-servers. Thus Wabi's behavior will be the same as it was in Wabi 1.1. (Wabi 1.1 wouldn't take advantage of an auxiliary font server process even if one had been started and was running.) If you want better performance rendering non-X11 (ex: TrueType) fonts, and are willing to accept some possibility of unstable behavior, enable Wabi's use of the auxiliary font server process for X-servers that support the font service protocol. To do this, edit $WABIHOME/lib/wabifs.displays, and un-comment the line corresponding to your display. If Wabi's behavior becomes unacceptably unstable, re-disable Wabi's use of its auxiliary font server process. NOTE: The newer Wabi kernel drivers for Solaris 2.4 were built on FCS versions of Solaris 2.4. 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 all users access (ex: -rw-rw-rw-).