|
|
Please take note of the following problems and workarounds when installing and using the Update Pack.
xAPIC support was designed for IBM x440 systems. On some platforms, such as the IBM xSeries 360 (x360), the OS detects it should use xAPIC but the platform does not properly support it. If this happens, the symptoms are device timeouts (either a disk driver or HBA) very early during the boot process. The system will display a message stating that an HBA or disk command has timed out, and the system will become unresponsive (hang). If you are using a Multi-Processing (MP) system with Pentium 4 (Xeon) processors and this occurs do the following:
Reset the system.
When the system displays the UnixWare logo during the boot sequence, interrupt the boot by pressing any key.
At the boot prompt enter:
USE_XAPIC=N boot
The system should now boot normally.
Once the system is running, edit /stand/boot and add the following entry to the file:
USE_XAPIC=N
This will ensure that you do not need to interrupt the boot process again.
A new dlpi driver tuneable in /etc/conf/pack.d/dlpi/space.c allows the administrator to turn off MAC header size prediction, which causes problems on IBM SNA Gateway systems:
/* * MAC header size prediction optimization: * * 0 => OS discovers the optimal MAC header size * <0 => disable MAC header size prediction optimization * >0 => use the MAC header size specified here */ int mac_header_size = 0;
To disable header size prediction, edit /etc/conf/pack.d/dlpi/space.c and change the value of
mac_header_size to -1.
Then enter the following commands to rebuild the kernel and reboot:
# idbuild -M dlpi # shutdown -i6 -g0 -y
This fix is contained in the nics package.
527969
You may see the following error during installation of the OpenSSH (openssh) package:
##Executing postinstall script. dynamic linker: /usr/sbin/sshd: could not open libcrypto.so.0.9.7 Killed /etc/init.d/opensshd: Error 137 starting /usr/sbin/sshd....Bailing.
This indicates that the OpenSSL (openssl) package is not installed; the installation of openssh,
however, will still report success.
To fix this, install the openssl package from the Update Pack 2 media
and then re-install openssh.
527982
If you install the Update Pack on a freshly installed UnixWare 7.1.3 system, you may see Warning messages during installation. This happens most commonly when you specify the correct local time when installing UnixWare 7.1.3, but select a locale whose timezone differs from the local timezone. As a result, there can be a mismatch between the current system time and the time stamp on the files installed from the Update Pack, which causes the following warning to be displayed:
WARNING: Reapply uw713u3 package. Failure to do so may leave your
system in an inconsistent state.
If this occurs, execute the following command:
pkginfo -l | grep INSTDATE | sort -u | more
Wait until the latest time returned by the above command has passed, and then reinstall the the uw713u3 package:
pkgadd -d device uw713u3
Where device is the location of the mounted Update Pack CD, CD image, or Update Set image.
527540
When launching the Upgrde Wizard using the uli command from a desktop window, the Upgrade Wizard
may exit unexpectedly if you press the space bar a few times while it is loading.
To work around this, re-run the Upgrade Wizard.
527905
During installation of the Update Pack on a system that was upgraded from a release prior to Release 7.1.3, warnings such as the following may be displayed:
UX:pkginstall: WARNING: /etc/conf/pack.d/msr/Driver.o <shared file is volatile> UX:pkginstall: WARNING: /etc/conf/pack.d/pcid/Driver.o <shared file is volatile> UX:pkginstall: WARNING: /etc/conf/pack.d/ppp/Driver.o <shared file is volatile> UX:pkginstall: WARNING: /etc/conf/pack.d/pppml/Driver.o <shared file is volatile> ...
The Warnings displayed on your system will depend on the originally installed release.
These Warnings are expected and can be safely ignored.
527406
Installing the cups package locks the Update Pack installation; you cannot remove the Update Pack after installing cups. This is due to the interdependencies that arise once the cups package is installed and enabled. If you want to remove the Update Pack, you must first remove the cups package, as in this example:
# chprnsys lp # pkgrm -n cups
The chprnsys command above ensures that System V LP is the current print subsystem, and the pkgrm
command removes cups.
Any related packages you installed along with cups should also be removed since they will not work properly once
the Update Pack is removed.
See Printing: CUPS (Common Unix Print Spooler).
528344
Problems have been observed with the DocView (http://hostname:8458) PRINT BOOK facility:
Some files do not print when selected from the PRINT BOOK list, or the incorrect content is printed instead. This occurs in C and non-C locales.
Multibyte files cannot be printed (this includes, for example, Japanese-language documentation from the jabasedoc package on the Localized Documentation CD in the UnixWare Media Kit) from the PRINT BOOK list. This is because the underlying engine in DocView for printing HTML (HTMLDOC) does not support multibyte files.
Some documents are not being printed in foreign languages when locale is properly selected and the foreign-language documentation is installed.
The workaround in all these cases is to display the files individually from the DocView SITE MAP interface (which is identical to the PRINT BOOK list), and use your browser's Print command to print the files.
For example, if you use the PRINT BOOK interface to print a New Features file
and it does not work, click on the SITE MAP button on the DocView menu (http://hostname:8458) and
select the name of the link that you wanted to print (the SITE MAP and PRINT BOOK lists are identical).
Once the document is loaded into the browser, print it using your browser's
Print command (File > Print in Netscape) to print to a local printer or
to a file.
The formats available depend on your local browser's setup.
527817
If you are installing the OpenServer Kernel Personality (OKP) product on top of the Upgrade Pack, do not add the OKP License to the License Manager before beginning installation of OKP. Instead, add the license during installation of OKP, as described in the OKP Release Notes. If you do add an OKP License to the License Manager before the OKP product is installed, the License Manager may report the following when you install the license:
Licensing of <Unknown Product with id 181> is successfully completed
Thereafter, the main License Manager screen may list the OKP license incorrectly, as follows:
Unknown Product with id 181
If this occurs, you should remove the OKP license
(License > Remove in the License Manager menu) and then add it again (License > Add).
The License Manager will then display the license correctly.
528252
If you remove the Update Set using the pkgrm(1M) command in an xterm window, the window may be changed to reverse video mode after the removal is complete. This does not indicate any problem with the removal of the Update Set. To return the window to normal video mode, enter:
tput reset
527620
CGI.pm is a Perl module (contained in the perl5 package available from the base UnixWare media) that provides function calls for form definition. There is a vulnerability present in forms created with the start_form() and start_multipart_form() functions defined in CGI.pm. If the action for the form is left unspecified in a call to either function, the form action can be manipulated by a malicious user (using an appropriate URL) to launch a cross site scripting attack against the host system.
If you use the CGI.pm module in any Perl programs, it is recommended that you install the
perl and perlmods packages, available
on the SCOx CD.
The perlmods package contains an updated CGI.pm module that closes this vulnerability.
528214
The samba and sambamb packages do not integrate the Samba documentation into docview or man; it is available only at http:localhost:901.
To integrate the Samba manual pages into the man(1) command, enter the following commands:
defadm man MANPATH=$MANPATH:/usr/lib/samba/man
makewhatis /usr/lib/samba/man/man.1 \
/usr/lib/samba/man/man.5 \
/usr/lib/samba/man/man.7 \
/usr/lib/samba/man/man.8
To integrate the Samba guide into DocView on htpp://localhost:8458 under Dos and Windows, do the following:
Create the file /usr/share/meta/doc/HelpTopics/DOShome/DOSgroup/samba.desktop with the following content:
[Desktop Entry] Name=Using Samba DocPath=/usr/lib/samba/swat/using_samba/index.html X-COL-rewrite=using_samba
Enter the following command:
/bin/doctool --add HelpTopics/DOShome/DOSgroup/samba.desktop
The Samba documentation and manual pages will be indexed automatically the next time DocView indexing is run.
528432The squid manual page installed by the squid package from the base UnixWare media contains a number of errors:
The Squid proxy server control script is located at /etc/init.d/squid.
The Squid software is located under /usr/lib/squid.
To start up Squid, your UnixWare system must already be connected to the internet, and the Domain Name Service (DNS) daemon in.named(1M) must be running. Squid must be able to reach at least one of the specified DNS servers; otherwise, it will not start. Follow this procedure to configure and begin using Squid:
Edit the file /usr/lib/squid/etc/squid.conf, and make the following changes:
visible_hostname keyword, and insert a line like the following:
visible_hostname nodename
where nodename is the name you want returned by the server to clients in messages.
Enable access for your clients.
This is done with a combination of the http_access and acl keywords (search for
http_access keyword; the acl section is just above it in the file).
To simply allow all hosts to access squid, enter a single http_access statement:
http_access allow all
Most sites will want better security, and allow only known sites to access the proxy. The following two statements allow only hosts on the "10.0.0" subnet to access the server:
acl local 10.0.0.0/255.255.255.0 http_access allow local
Note that the ordering of http_access entries in the squid.conf file is important.
You may need to put entries for local clients at the top of the list of http_access entries
in order for them to work.
See the comments in the file /usr/lib/squid/etc/squid.conf as well as the Squid documentation installed along with the squid package, in the online documentation under Internet and Intranet, for more information on configuring Squid.
Enter, as root:
/usr/lib/squid/bin/squid -z
to initialize the Squid caches.
Start Squid:
/etc/init.d/squid start
On each client (including the local system), set the browser's preferences to go to the proxy server instead of connecting directly to the internet. In Netscape or Mozilla, this is done by opening the browser Preferences (Edit > Preferences) and selecting Advanced > Proxies. Select Manual Configuration, and click on View. In the following window, set at least the http: and ftp: entries to point to the nodename or IP address of the UnixWare system running the Squid proxy server; then, set the port for both entries to 3128, the default port on which the UnixWare Squid server listens for requests. Save your changes to the browser's Preferences.
The browser will now access the internet through the Squid proxy. Check the files under /usr/lib/squid/logs if you encounter problems.
© Copyright 2003 The SCO Group, Inc. All rights reserved.