Release 7.1.0 Software notes

Before you install or upgrade your system

Please read through the following limitations to determine if any apply to your system: each limitation has a workaround that will allow you to install or upgrade your system successfully.


Fresh or upgrade installation: security fix
In UnixWare 7 Release 7.1.0, unnecessary privilege has been given to some packaging commands, and as a result system security can be compromised. The solution is to remove the unnecessary privilege from these commands. This is a temporary work-around to the problem, not a production solution. SCO will be producing a software solution in the very near future, but we are informing you immediately of the problem so that you can take immediate action to preserve the integrity of your system.

We strongly recommend that immediately after installing UnixWare 7 Release 7.1.0 you execute the following commands while logged into the system as root:

filepriv -d /usr/sbin/pkgadd
filepriv -d /usr/sbin/pkgrm
filepriv -d /usr/bin/pkginfo
filepriv -d /usr/bin/pkgparam
filepriv -d /usr/sbin/pkgchk
filepriv -d /usr/bin/pkgtrans
filepriv -d /usr/sadm/install/bin/pkgremove
filepriv -d /usr/sadm/install/bin/pkgaudit
filepriv -d /usr/sadm/install/bin/pkgname
filepriv -d /usr/sadm/install/bin/pkginstall

If you need to grant privilege to a user, the system owner, for example, then this can be accomplished in the following way as root:

/bin/adminuser -n -a pkgadd:/usr/sbin/pkgrm:dacread:dacwrite user_name
/bin/adminuser -a pkgrm:/usr/sbin/pkgrm:dacread:dacwrite user_name

The system owner, user_name, can then execute pkgadd or pkgrm as follows:

/sbin/tfadmin /usr/sbin/pkgadd
/sbin/tfadmin /usr/sbin/pkgrm

A side-effect of this temporary work-around is that network installations will fail if the above measures are applied to the network install server. If it is vital for you to be able to perform network installations then we strongly suggest that you disable non-administrative user accounts on the server.


Fresh installation: Installation failure from driver resource address conflicts
UnixWare 7 does not accurately detect some driver resource conflicts which can occur during installation between the PC-Card subsystem driver (pcic) and certain configurations of host bus adapters. When such problems occur the kernel re-link fails and a red error screen appears at the end of license installation.

The kernel relink problem occurs because the pcic driver, which is configured initially to determine if the system has PC Card support, may claim the same ISA memory addresses that are used by other hardware drivers such as host bus adapter drivers. The resources used by the pcic driver include the memory address range of 0xD0000-0xD1FFF and the I/O address range of 0x3E0-0x3E7.

You can resolve the problem during installation by entering the DCU and disabling the pcic driver. The pcic driver can be identified in the dcu as the driver that uses the resources above with a Device Name of "Card & Socket Services". The pcic driver can be safely disabled since the pcic driver is only useful on machines such as laptops which provide PC Card slots.


Fresh installation: installing language extensions for non-C locales
If you install in English and select an English (or C) locale on installation, the appropriate language extensions packages will not be installed if you later want to run your system in another locale/language, such as in French (fr_FR). This affects the ability to run the International Settings Manager correctly, among other limitations.

There are two workarounds:

After you install the desired package(s), you can set your system to run in the desired locale using the International Settings Manager.


Fresh installation: installing multiprocessor support (osmp)
By default, multi-processor platform support is only selected for the Data Center edition. To enable this support on other editions that license it, you must select Customize installation of packages during the installation and select the Multiprocessor package (osmp) from Core Operating System Services in the Base set.

Fresh installation: spurious HBA drivers loaded
During installation of UnixWare 7 Release 7.1, some HBA drivers may load even when there is no hardware present for them. This is not likely to cause problems, as these drivers will automatically be turned off when the system is next rebooted.

To prevent the drivers from loading during the installation, enter the DCU when prompted, choose Software Drivers, and de-select any unwanted drivers.


Fresh installation: swap space on smaller-memory systems
If you are performing a fresh installation on a system with up to 64MB of Random Access Memory (RAM), the installation program might not allocate adequate swap space for you to perform the installation successfully.

To view the swap space allocated, choose to Customize filesystems and slices when prompted during the installation.

You should have at least this much swap space allocated to successfully install UnixWare 7 Release 7.1:

RAM (MB) Swap space (MB)
32 96
48 120
64 144


Upgrade installation: swap space on smaller-memory systems
As in the previous note, the Upgrade Wizard requires an adequate amount of swap space to upgrade your system.

To determine the amount of swap allocated on your system, enter:

df -v

If the size of /dev/swap is not equal to or greater than the values shown in the previous note, you need to add swap space before running the Upgrade Wizard. Refer to "Adding swap space" in SCOhelp and the swap(1M) manual page for information on how to add a swap file to the system.


Upgrade installation: run in foreground
The Upgrade Wizard should only be run in the foreground. If you want to have access to a shell prompt while running the Wizard, open another terminal window or switch to the console screen.

Upgrade installation: SCO Merge installation
You should neither install nor upgrade SCO Merge from within the Upgrade Wizard. Doing so might cause your system to panic on reboot.

Instead, upgrade the other packages you desire, then use the Application Installer or pkgadd(1M) to install SCO Merge.


Upgrade installation: possible kernel build failure
Using the Upgrade Wizard to upgrade your system from Release 7.0.1 to Release 7.1, or to load additional packages onto a Release 7.1 system, might result in a kernel build failure when you shut down the system at the end of the upgrade procedure. This is caused by unnecessary HBA drivers being loaded onto the system, and results in an error similar to this on re-link:
   UX:idmkunix: ERROR: Conflicting use of interrupt vector; already
   used as type 4, ipl 5
If this happens, you can still boot your system and remove the unwanted HBA drivers using pkgrm, then rebuild the kernel and reboot the system.

Complete details on this problem, including a script to help you determine which drivers can be removed, will be posted to a new technical article at at the SCO Support Library.


Upgrade or fresh installation: incorrect permissions on /tmp
An error in the installation scripts for the Compaq Hot Plug Controller Driver package (cpqhpcd) leaves the /tmp directory with incorrect permissions. This disables the ability of users to write to /tmp; for example, SCOadmin will not start due to an inability to write log information.

This error only affects those installing the Compaq Hot Plug Controller Driver package. If you do install this package, perform your installation or upgrade as normal, then log into the system as root and issue the following commands:

chmod 1777 /tmp
chown base /tmp
chgrp sysutil /tmp


© 2001 The Santa Cruz Operation, Inc. All rights reserved.